[RISC-V] Large number of CLR tests failing and significant test count reduction on latest main #122043
Description
Description
On the latest main (commit 7da7284), a large number of RISC-V CLR bringup tests fail, and the total number of CLR tests discovered is significantly smaller than in previous commits.
Reproduction Steps
Environment
- linux.riscv64.Checked
- QEMU
- commit 7da7284
Expected behavior
Less failures in bringup test and more tests discovered in CLR test
Actual behavior
bringup tests
=======================
Test Results
=======================
# CoreCLR Bin Dir :
# Tests Discovered : 1837
# Passed : 1410
# Failed : 405
# Skipped : 22
=======================
CLR tests
Time [secs] | Total | Passed | Failed | Skipped | Assembly Execution Summary
============================================================================
300.521 | 215 | 215 | 0 | 0 | JIT.Directed.Directed_2
51.191 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests700-799
58.589 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests1300-1399
59.332 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests800-899
23.149 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests500-599
21.699 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests100-199
44.256 | 101 | 101 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests1400-1599
44.892 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests600-699
10.268 | 3 | 3 | 0 | 0 | JIT.JIT_do
24.282 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests400-499
1.663 | 0 | 0 | 0 | 0 | JIT.Regression.Regression_PdbOnly_r
63.167 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests1000-1099
1.178 | 0 | 0 | 0 | 0 | managed.Managed
1.554 | 0 | 0 | 0 | 0 | JIT.Regression.Regression_PdbOnly_r_4
58.045 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests1200-1299
59.636 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests1100-1199
17.922 | 13 | 13 | 0 | 0 | ilasm.ilasm_tests
9.213 | 2 | 2 | 0 | 0 | JIT.JIT_d
28.803 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests300-399
63.681 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests900-999
21.237 | 81 | 81 | 0 | 0 | JIT.jit64.jit64_1
23.362 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests0-99
30.585 | 100 | 100 | 0 | 0 | Loader.classloader.TypeGeneratorTests.TypeGeneratorTests200-299
1.707 | 0 | 0 | 0 | 0 | JIT.Regression.Regression_r_1
1.702 | 0 | 0 | 0 | 0 | JIT.jit64.jit64_4
----------------------------------------------------------------------------
1021.637 | 1815 | 1815 | 0 | 0 | (total)
Regression?
This issue does not occur on commit d108713.
Note that this may not be the latest known-good commit.
Known Workarounds
No response
Configuration
No response
Other information
To check whether this is not an environment issue on our side, I attempted to trigger the RISC-V CLR tests using @risc-vv /run in #122028, but it seems that only public members of the repo are allowed to use this command.