Open stephan-herrmann opened 5 months ago
@iloveeclipse has an initial result in this comment
If this is broken at all, it probably broken at the test report or creation level (org.eclipse.jdt.core.tests.junit.extension.TestCase.buildTestsList(Class, int, long) ?), I see that there are tests from ScannerTest like testBug531716_001_since_13 but they are marked as org.eclipse.jdt.core.tests.compiler.regression.TestAll.
OMG, you're right, there are 196 results for "test034", only 2 of which are assigned to a specific test class.
At the end of org.eclipse.jdt.core.tests.compiler.regression.TestAll.suite()
the structure looks like this:
This runtime structure looks OK and I'm not aware of anything that might have changed here in years.
How does the I-build create & collect test results?
The file is not incomplete. jenkins reads the result from an .xml which is generated when the tests run https://ci.eclipse.org/releng/job/AutomatedTests/job/ep432I-unit-cen64-gtk3-java17/lastSuccessfulBuild/artifact/workarea/I20240520-1800/eclipse-testing/results/xml/org.eclipse.jdt.core.tests.compiler_ep432I-unit-cen64-gtk3-java17_linux.gtk.x86_64_17.xml
`
`
I never figured out how exactly the values inside the .xml are generated, but both Testnames and time are reproducible wrong. The testname probably is wrongly setup in the junit test/suite itself.
I was searching for recent test results for this test:
org.eclipse.jdt.core.tests.compiler/org.eclipse.jdt.core.tests.compiler.regression.ScannerTest.test034()
But in none of the recent test results like I20240519-1800 I could find any trace of the test. In fact searching for.ScannerTest
shows exactly 5 matches while 86 matches should be expected.By contrast, github-triggered builds like https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Github/job/master/222/testReport/org.eclipse.jdt.core.tests.compiler.regression/ScannerTest/ show the expected number of tests (here multiplied with 5 for 5 compliance levels).
Going back all the way to 4.29 it shows 18 tests, still far from complete.