=dev-java/testng-6.11 fails its test phase for me. Specifically, the section "Parallelization" reports =============================================== Parallelization Tests run: 76, Failures: 4, Skips: 0 =============================================== Those four failures look like four instances of FAILED: verifyThatTestMethodsRunInParallelThreads Each instance of that in the log is followed by a very long line that begins java.lang.AssertionError: The expected maximum number of methods to execute simultaneously is 20 for TestSuiteB-ThreeTestClassTest so no more than 20 methods should be executing at the same time. Event logs: followed by four lines of stack trace, followed by "... Removed 27 stack frames"
Created attachment 876403 [details] dev-java:testng-6.11:20231202-145859.log
Created attachment 876404 [details] emerge-info.txt
(In reply to Jonathan Lovelace from comment #0) > =dev-java/testng-6.11 fails its test phase for me. Specifically, the section > "Parallelization" reports > [...] Thanks for reporting. I am sorry but I cannot reproduce those test failures. In case you would like to help boil it down to the root cause: - Are these failures reproducible, always same tests with same message? - Does it also happen with USE"-test"? - Does it also happen with Java 1.8, 11 or 21?
I see essentially the same output (likely different Java object addresses in the CLASS_INSTANCE values late in the assertion message, timestamps of course differ, etc.) every time so far running this test suite on this machine. I tried with openjdk-8 and openjdk-11 (using "JAVA_PKG_FORCE_VM=openjdk-8 ebuild /path/to/testng-6.11.ebuild clean install clean", etc.), with the same results. This machine (being a "mostly-stable" box) didn't have a Java 21 JDK installed, but I installed openjdk-bin-21 and got the same results with it. Because java-utils-2.eclass defines RESTRICT="!test? ( test )", when I tried running the build with USE="-test" it skipped running tests entirely: "Skipping make test/check due to ebuild restriction."
(In reply to Jonathan Lovelace from comment #4) > [...] > Because java-utils-2.eclass defines RESTRICT="!test? ( test )", when I tried > running the build with USE="-test" it skipped running tests entirely: > "Skipping make test/check due to ebuild restriction." Sorry, my fault. What I meant to ask is about USE=-doc
Same failure with USE=-doc (with openjdk-17).
