I've seen that happen on Windows only, which this is not. On Windows this seems to be a MongoDB packaging bug which surfaces as:
https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/232 and https://jira.mongodb.org/browse/SERVER-32877 But since this is Linux... I'll try the same workaround I do on Windows, which is to _not_ use the latest MongoDB version but fix the test to version 3.4. Gary On Sun, Feb 18, 2018 at 12:39 AM, Ralph Goers <[email protected]> wrote: > The mongo db test failed. > > Ralph > > > > On Feb 18, 2018, at 12:35 AM, Apache Jenkins Server < > [email protected]> wrote: > > > > See <https://builds.apache.org/job/Log4j%202%203.x/1/display/redirect> > > > > > > >
