br0nstein commented on PR #545: URL: https://github.com/apache/maven-surefire/pull/545#issuecomment-1226895900
@Tibor17 thanks please let me know how we can go from here to get this problem fixed. Should we try to update the test to actually crash the JVM at runtime rather than cause JVM startup to fail in case that were to be caught by failsafe differently? Not sure if there are any ripe unpatched JVM bugs that we could utilize, heh. Want to double check that we do want to pursue this approach of causing the verify phase to fail rather than treat this like non-crashing failing tests with test.failure.ignore enabled, by writing out some test result XML that Jenkins/etc could pick up to treat as "unstable." -- 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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
