-
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
Interop.0.1 failing on gcstress pipeline #99001
Comments
Ping @mangod9. It is still failing in gcstress pipelines. |
This is from the weekend and I know @janvorli has made some changes related to it. Also adding @AaronRobinsonMSFT since this is an interop failure. |
@kunalspathak please turn this to a known issue format, It is happening more widely for all tests in gcstress0xc pipeline. |
This doesn't seem to be related to anything I was working on. The failure assert / stack trace is as follows. It fails because
|
The etype argument is ELEMENT_TYPE_END in this case. |
And this is the stack trace from
|
(This is a dump from my PR where I've hit the issue too, obtained by All architectures / OSes were failing in this test, including Windows x86: https://dev.azure.com/dnceng-public/public/_build/results?buildId=588479&view=ms.vss-test-web.build-test-results-tab&runId=14198304&resultId=168380&paneView=debug |
Yes, this is fixed with #99253.
@kunalspathak This is not good ErrorMessage pattern. It is very generic and it is going to match a lot of unrelated failures. 2 out of 3 matches above are unrelated to this issue. A better error message pattern would be |
Ah, ok. Thanks for letting me know. |
https://dev.azure.com/dnceng-public/public/_build/results?buildId=578218&view=results
I see some failures like:
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=578218
Error message validated:
[Internal CLR error
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/5/2024 1:18:23 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: