voonhous commented on issue #19910: URL: https://github.com/apache/hudi/issues/19910#issuecomment-5653906635
Test-count parity, master against the campaign's end state, counted from every job log of [master run 34674848405](https://github.com/apache/hudi/actions/runs/34674848405) and [#19937's attempt 3](https://github.com/apache/hudi/actions/runs/34753265152/attempts/3) plus its engine run. The question was whether any test stopped running along the way. ScalaTest, identical: | | master | end state | |---|---|---| | passed / failed / canceled / ignored | 963 / 0 / 5 / 3 | 963 / 0 / 5 / 3 | | distinct test names | 986 | 986, the same set | Surefire, 0 failures on both sides, 1285 against 1287 classes, 9 classes with a different count and every difference explained: | | master | end state | |---|---|---| | tests run | 19267 | 17470 (Trino plugin excluded: its run is not part of master's Java CI) | | skipped | 214 | 215 | - 1808 duplicate runs removed: master ran the 113 hudi-flink test classes twice, in flink-2 and again in common-and-other; #19909 dropped the second run, the end state runs each once. - Utilities tests moved jobs: 1718 on master split between common-and-other and test-utilities, 1721 on the end state in the two utilities jobs, same classes. - TestHoodieDeltaStreamer is four classes since #19892: 197 against 199. - The bloom filter benchmark is out of unit runs by design in #19892: 1 test. - Two new unit tests from #19935 and #19936. - A few classes whose methods surefire's two forks report as two partial summaries; the totals match. No class runs fewer tests on the end state than on master. The same paragraph is in the findings list above. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
