-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
tracing/eventpipe/eventsourceerror/eventsourceerror failing in local coreclr test run #56633
Comments
Tagging subscribers to this area: @tommcdon Issue DetailsI have this test failing consistently if run as part of the coreclr test suite locally on my Linux dev box. Running it standalone doesn't repro the issue for me. This is the test error output:
|
cc: @josalem |
I'll see if I can repro this locally. Do you happen to know which assert in DecodeObjects is getting hit? This being inconsistent has me perplexed. When you say "part of the coreclr test suite" do you mean running everything using the xunit infrastructure vs just invoking the generated cmd/sh file if you build the test directly? |
Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti Issue DetailsI have this test failing consistently if run as part of the coreclr test suite locally on my Linux dev box. Running it standalone doesn't repro the issue for me. This is the test error output:
|
Yes, I meant running all the tests using src/tests/run.sh vs running the test standalone using its generated .sh. Here are the steps just to make sure we are on the same page:
There are actually two more profiler / tracing tests that that fail in a similar manner, the profiler/unittest/getappdomainstaticaddress and tracing/eventpipe/gcdump/gcdump. I've seen them fail regularly in the past too locally. Let's see if you can repro it locally. |
I haven't had a chance to try and repro this, but in the hopes of triaging this further I scanned |
Moved to .NET 7. The Assert that is failing is new to .NET 6, but the issue is likely pre-existing. |
@janvorli before I pick this issue back up, do you still see these failures? I don't believe we turned any of the tests off in response to this issue, so they have presumably been working in CI since your report. |
@josalem let me give it a try and see. |
@josalem I cannot repro the issue anymore. I am closing the issue. |
I have this test failing consistently if run as part of the coreclr test suite locally on my Linux dev box. Running it standalone doesn't repro the issue for me.
This is the test error output:
The text was updated successfully, but these errors were encountered: