-
Notifications
You must be signed in to change notification settings - Fork 5k
Test failure profiler/eventpipe/eventpipe/eventpipe.sh #66174
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
Comments
This timeout is pervasive: Kusto data shows that it happens in many pipelines, but mostly on osx/x64. @dotnet/area-system-diagnostics-tracing |
This happened again for rolling build #20220308.1 on |
This is now blocking the runtime builds as well @tommcdon could someone take a look asap? |
@agocke taking a look |
Here's where it started failing for the nightly scheduled jitstress run: |
There's a few families of errors in here. Most of them were old and targeted to specific PR's There's this:
These type of simd asserts that have been reported elsewhere:
All the ones that come from the profiler test itself are timeouts in OSX, regardless of jit modes. |
@hoyosjs Why did you remove the "blocking-outerloop" label? Unless this test has been fixed or disabled, it is, indeed, blocking clean outerloop test runs. |
Failed again in: runtime-coreclr jitstress-isas-x86 20220312.1 Failed test:
Error message:
|
Should the test be disabled for now? I saw this being hit on rolling build quite often. |
Note: this test was disabled in #66606. Re-enable when fixing/closing this issue. |
@davmason PTAL |
Run: runtime-coreclr outerloop 20220303.2
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: