You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@flink.apache.org by Flink CI <fl...@foxmail.com> on 2020/02/25 11:51:09 UTC

Still Failing: apache/flink#42652 (release-1.10 - 02255ed)

|  [

apache

/

flink

](https://travis-ci.org/apache/flink)  
---  
  
![branch icon](https://s3.amazonaws.com/travis-email-
assets/branch.png)[release-1.10](https://github.com/apache/flink/tree/release-1.10)  
  
|

![build hasfailed](https://s3.amazonaws.com/travis-email-assets/status-
failed.png)

[Build #42652 still failing](https://travis-
ci.org/apache/flink/builds/654812524)

![arrow to build time](https://s3.amazonaws.com/travis-email-assets/failure-
arrow.png)

![clock icon](https://s3.amazonaws.com/travis-email-assets/time.png)1 hour, 50
mins, 57 secs  
  
---  
  
![Andrey Zagrebin
avatar](https://secure.gravatar.com/avatar/d0819e195ae69a7b66bb124b366ac9de.jpg)Andrey
Zagrebin

[02255ed CHANGESET
->](https://github.com/apache/flink/compare/82f6dc2dbcf1...02255ed8996a)  
  
[FLINK-15094] Use Unsafe to instantiate and construct DirectByteBuffer  
  
If we use reflection to create a DirectByteBuffer to wrap unsafe native memory
allocations,  
it causes illegal access warnings in Java9+.  
This PR changes this to use Unsafe to instantiate a DirectByteBuffer.  
The address and capacity fields are set by direct unsafe memory operations.  
Other fields are set by calling ByteBuffer#clear at the end.  
Unsafe operations skips the illegal access verification and do not result in
warnings.  
  
This solution still relies on Unsafe which is about to be removed in future
Java releases.  
If it is removed and we still do not want to contribute to direct memory by
allocating native managed memory,  
we will have to find alternartive solutions, like e.g. writing a custom native
allocator  
and use JNI API to instantiate the wrapping DirectByteBuffer
(NewDirectByteBuffer in C).  
  
This closes #11160