-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Failure - jit64_do.0.1
#85590
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Detailsruntime-coreclr gcstress0x3-gcstress0xc
|
@TIHan Please include a link to the failure pipeline and indication of which configuration failed. In this run: I see all the failures are in jit64 tests with GCStress=3. Most are timeouts (@markples -- more GCStress timeouts in merged groups) win-x64 failure is:
perhaps that's also a symptom of timeout, since it's the last test run? |
Sure, will do. |
This includes several changes that seem to help with the timeouts. It might be overkill but seems like a good direction as this has been broken for a while. - Change the test wrapper logic to only put one test in a TestExecutor so that the callstacks are much simpler. - Factor the test wrapper logic into some helpers to simplify the main method. I also tried to make the "Full" and "XHarness" code generation very similar but didn't try to factor/unify them. - Mark several tests as RequiresProcessIsolation so that their gcstress is kept separate from the rest of the tests. Disables a large test under gcstress. - Add gcstress striping to some merged groups. Should fix #85590
Link
runtime-coreclr gcstress0x3-gcstress0xc
The text was updated successfully, but these errors were encountered: