On Sat, Apr 7, 2018 at 12:15 PM, Matt Sicker wrote:
> In this build [1], it appears to be failing in some Windows MongoDB
> integration tests. Might be a file permission assumption?
>
Could be a corrupt download:
java.io.IOException: File
Everything builds and tests fine for me on macOS using master. Interesting.
On 7 April 2018 at 14:06, Carter Kozak wrote:
> I've been having issues with EquinoxLoadApiBundleTest,
> FelixLoadApiBundleTest, and FileAppenderPermissionsTest (has some
> special casing on osx which
In this build [1], it appears to be failing in some Windows MongoDB
integration tests. Might be a file permission assumption?
[1]:
https://builds.apache.org/job/Log4jCore/job/master/17/execution/node/27/log/
On 7 April 2018 at 11:48, Gary Gregory wrote:
> There was a
I've been having issues with EquinoxLoadApiBundleTest,
FelixLoadApiBundleTest, and FileAppenderPermissionsTest (has some
special casing on osx which may not be compatible with my environment,
works on linux though) on osx, haven't had a chance to dig into them
quite yet.
I've executed the tests
There was a commit today or last night, I think about messages and
parameters, maybe it is related.
Gary
On Sat, Apr 7, 2018, 10:22 Matt Sicker wrote:
> I'm actually getting the same test failures on macOS now. Might just be a
> regression.
>
> On 7 April 2018 at 11:15, Matt
https://builds.apache.org/job/Log4jCore/job/master/16/execution/node/38/log/?consoleFull
I'm not exactly sure what this error is. Did I misconfigure this job
entirely? This test doesn't seem to fail on the Ubuntu build.
--
Matt Sicker
I'm actually getting the same test failures on macOS now. Might just be a
regression.
On 7 April 2018 at 11:15, Matt Sicker wrote:
> https://builds.apache.org/job/Log4jCore/job/master/16/
> execution/node/38/log/?consoleFull
>
> I'm not exactly sure what this error is. Did I
Carter,
To me it’s sufficient due diligence when you’ve run the tests on your machine.
The continuous integration builds are a smoke test to flush out issues on other
environments. They sometimes show issues none of us see when building locally.
I would only consider a failing test to break