You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by bjlaub <gi...@git.apache.org> on 2018/08/06 20:28:36 UTC
[GitHub] logging-log4j2 pull request #201: workaround flaky "Operation not permitted"...
GitHub user bjlaub opened a pull request:
https://github.com/apache/logging-log4j2/pull/201
workaround flaky "Operation not permitted" failures in mongo tests
mongo tests intermittenly fail with an "Operation not permitted"
IOException when trying to execute the mongod extracted by
de.flapdoodle.embed.process; this seems to be related to surefire
running tests in parallel. Work around that here by forcing serial
execution of the mongo tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bjlaub/logging-log4j2 fix-flaky-mongo-tests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/201.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #201
----
commit ce775cfe375ce9cfc4703fd701fdb6ac07d3eebb
Author: Brian Laub <bj...@...>
Date: 2018-08-06T20:15:19Z
workaround flaky "Operation not permitted" failures in mongo tests
mongo tests intermittenly fail with an "Operation not permitted"
IOException when trying to execute the mongod extracted by
de.flapdoodle.embed.process; this seems to be related to surefire
running tests in parallel. Work around that here by forcing serial
execution of the mongo tests.
----
---
[GitHub] logging-log4j2 pull request #201: workaround flaky "Operation not permitted"...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/201
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by garydgregory <gi...@git.apache.org>.
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
Is this needed for module log4j-mongodb3 as well?
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by garydgregory <gi...@git.apache.org>.
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
Go for it.
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by cakofony <gi...@git.apache.org>.
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
@garydgregory I'm going to merge this commit later today given that this is the first time in recent memory that travis has passed tests. Please let me know if you'd prefer that I hold off.
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by cakofony <gi...@git.apache.org>.
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
We do the same thing in log4j-core [here](https://github.com/apache/logging-log4j2/blob/master/log4j-core/pom.xml#L384-L385)
Is this module inheriting from the root pom.xml? https://github.com/apache/logging-log4j2/blob/master/pom.xml#L1101-L1112
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by cakofony <gi...@git.apache.org>.
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
Merged, thanks!
---
[GitHub] logging-log4j2 issue #201: workaround flaky "Operation not permitted" failur...
Posted by garydgregory <gi...@git.apache.org>.
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/201
Also, I thought {{forkCount=1}} was the default?
---