-
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
TypeTests.Get, JitInfoTests, and EnumTests Fail with TestReadyToRun #94189
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsPR #91229 adds a new pipeline to run libraries tests with ReadyToRun, by means of the MSBuild flag To reproduce the issue: # Get the runtime repo
git clone https://github.com/dotnet/runtime
cd runtime
# Build the clr and libraries
./build.sh --subset clr+libs --configuration Release
# Run the smoke libraries tests with TestReadyToRun enabled
./build.sh --subset libs.tests --configuration Release --test -p:TestReadyToRun=true -p:RunSmokeTestsOnly=true Here's an extract of the log with the failing tests:
|
I'm changing the area to crossgen2 - this is not an infra issue - some of this looks like a test issue where the test needs to be adapted, other looks like actual product bug in crossgen2. |
PR #91229 adds a new pipeline to run libraries tests with ReadyToRun, by means of the MSBuild flag
-p:TestReadyToRun=true
. However, there are a few tests that are currently incompatible with TestReadyToRun. This issue is to track the necessary work to fix them.To reproduce the issue:
Here's an extract of the log with the failing tests:
The text was updated successfully, but these errors were encountered: