I tried to fix the Travis build but I don’t know what to specify for the JDK
paths for the toolchains.xml and don’t know who to ask.
Ralph
> On Aug 25, 2019, at 12:15 PM, Matt Sicker wrote:
>
> This is a known issue with our Travis config. I'm surprised that we
> don't have Jenkins configured
FWIW, the memory mapped file appender fails when you run the perf tests. I had
to comment it out. I don’t recall what the problem was.
Ralph
> On Aug 25, 2019, at 9:27 AM, Carter Kozak wrote:
>
> JEP 352: Non-Volatile Mapped Byte Buffers: https://openjdk.java.net/jeps/352
> This sounds interes
This is a known issue with our Travis config. I'm surprised that we
don't have Jenkins configured to test PRs, though I guess that might
be because Travis used to work fine for that.
On Sun, 25 Aug 2019 at 13:43, gaurav wrote:
>
> Hi devs,
>
> I've created a pull request on github.
>
> https://gi
Hi devs,
I've created a pull request on github.
https://github.com/apache/logging-log4j2/pull/305
Here's the travis build failure url -
https://travis-ci.org/apache/logging-log4j2/builds/576515115
Thanks,
Gaurav
JEP 352: Non-Volatile Mapped Byte Buffers: https://openjdk.java.net/jeps/352
This sounds interesting! I'm curious what kind of performance impact we could
see in practice.
Regarding the repository configuration, I'm surprised we don't have tooling
available to handle our use case, there must be
It’s still super early in the JDK 14 development cycle (13 is in release
candidate phase as mentioned earlier), though one of the interesting new
features in development there is a standard API to access NVMe storage as a
ByteBuffer. Not only that, but there’s work being done to support long in
add
