-
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
Attributes.OnlyKeepUsed.NullableOnConstraints failing in dotnet-linker-tests #90431
Comments
Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr, @marek-safar Issue DetailsError Blob{
"ErrorMessage": "Failed Attributes.OnlyKeepUsed.NullableOnConstraints",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
} Failure:
Reproduction StepsNo response Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=371500&view=results
|
Locally I saw that this started happening with the update to preview 7 in 5549f72. It looks like it has something to do with NullableAttribute definition being moved to the framework instead of generated into the output assembly, but I haven't root caused it yet. I also need to check why the update PR didn't hit this. |
Looks like the linker tests are running during the build so this infrastructure can’t identify them unless we ignore all failures from those tests. |
The update PR didn't catch this because the illink test jobs only run for changes to the tools.illink subset: runtime/eng/pipelines/common/evaluate-default-paths.yml Lines 135 to 137 in 39c0dbf
Most of the other jobs specify at least some exclude paths, which has the counterintuitive effect that all paths not specified in the exclude paths (including for example global.json) will be evaluated for changes.
|
Error Blob
Failure:
Reproduction Steps
No response
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=371500
Error message validated:
Failed Attributes.OnlyKeepUsed.NullableOnConstraints
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 8/11/2023 9:53:00 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: