kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873987237
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-874450203
> Closing as not willing to read tons of text.
Great reason, thank you so much.
> I do not have time to read kilobytes of text for simple issues.
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-874045506
Of course you know better than me, which is why I sent my RFC about the open
issue (zombie Java processes) in the first place. Now you finally have
acknowledged that
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873987237
What are you talking about? I don't wanted to write so much, but obviously
didn't understand that this is a real problem and didn't care to investigate by
yourself or
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873766789
I just found https://issues.apache.org/jira/browse/MSHARED-867 and left a
comment. It could be related to the problem described here.
--
This is an automated message
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873764177
Please note my update at the end of
https://github.com/apache/maven-surefire/pull/355#issuecomment-873703758
concerning differences in leftover zombie processes between
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873712057
> Here is the [history
](https://github.com/kriegaex/maven-surefire/commits/before-SUREFIRE-1881)of
commits in your repo - no fix!
You don't get it, do you? This
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873703758
> You did not take my commit with the fix. Your HEAD commit in your
repository contains your tests without the fix. So it is quite irrelevant.
What are you talking
kriegaex commented on pull request #355:
URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873560441
According to the CI results, now `Surefire1881IT` is actually (and
successfully for both cases) executed. So far, so good. Why in one case on
MacOS
