-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
System.Linq.Expressions tests are broken in CI #51346
Comments
Tagging subscribers to this area: @cston Issue Details
|
Pinging the authors of the latest changes in src\coreclr: @kunalspathak @SingleAccretion @davidwrighton @MichalStrehovsky @BruceForstall @trylek @jkoritzinsky |
Sigh. This is caused by #50450 - we are now folding the cases when
It has the same root cause as #47374, and the fix is blocked by resolving #47478. I will put up a PR to disable these for now. @eerhardt I assume the log you have contains all the failures, right? |
I think so. |
@SingleAccretion going to assign this to you. Let me know if you're not able to get to this sometime in the next week or two. |
I have a PR up that will re-enable these tests: #53782. I will switch it as ready-for-review. |
* Enhance the FloatOvfToInt2 test to exercise VN paths It is not very effective right now because the "bad" combinations of types are morphed into helpers too early, but it will be helpful when we enable folding outside of the importer for those cases too. * Enhance the FloatOvfToInt2 test to cover importer It now fails on Windows x86, where many of the previous similar failures were observed. * Disable the test on Mono * Re-enable tests disabled against #13651 * Re-enable tests disabled against #51346 * Re-enable tests disabled against #47374 * Disable folding in gtFoldExprConst * Disable folding in VN * Temporarily promote the test to Pri0 * Reword the comment * Move the tests back to Pri1 Where they originally were.
The text was updated successfully, but these errors were encountered: