Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/177
@Tibor17 I have tested this patch and I confirm that with this change the
error is the same as you are reporting, that is there is no more "Corrupted
stream" but only
> [WARNING]
Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/177
@Tibor17 I will be happy to pick up this issue and continue the work. I am
an user of the feature. I will continue the work as soon as I have time
---
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/177
Maybe not necessary to test it again because I downloaded logs from our
Jenkins ans I see the IT
JUnit48TestCategoriesIT_testBadCategoryForkAlways
which has the Warning message in
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/177
@eolivelli
Pls check it our with your code. The log should not appear in the dump file.
---
Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/177
I think that in "Branch Sources" you have to enable GitHub and work with
"iscover pull requests from forks" options.
It is a kind of Jenkins Job I have never used.
Usually I
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/177
@eolivelli
If you know how to do it in CI, just tell me.
You can see CI Mulibranch Pipeline in
https://builds.apache.org/job/maven-wip/job/maven-surefire/
---
