I'm actually getting the same error in Travis. Same MongoDB 2 test with the
embedded Mongo. See build log here: <
https://api.travis-ci.org/v3/job/363822919/log.txt>
On 8 April 2018 at 12:00, Matt Sicker wrote:
> Jenkins info:
>
> Apache Maven 3.5.2
Jenkins info:
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T07:58:13Z)
Maven home: f:\jenkins\tools\maven\latest3\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation
Java home: f:\jenkins\tools\java\latest1.8\jre
Default locale: en_US, platform encoding: Cp1252
FWIW, I just ran a local build of master and 'mvn clean install' with:
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T12:49:05-07:00)
Maven home: C:\Java\apache-maven-3.5.3\bin\..
Java version: *1.8.0_162*, vendor: Oracle Corporation
Java home: C:\Program
Same here. I don't have any Windows machines for development available, so
I brought this up here to see if any Windows devs had any ideas. I'd set up
a macOS CI build on Travis as well, but half of us are developing on macOS
anyways, so it seems less important. Testing on GNU/Linux, however, has
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
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
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
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
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
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
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
11 matches
Mail list logo