Enable alljitcommunity in CI #114325
Merged
Enable alljitcommunity in CI #114325
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-policy-service
bot
added
the
community-contribution
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
eng/pipelines/coreclr/superpmi-diffs.yml:58
- Ensure that the 'clr.alljitscommunity' argument is supported in all targeted environments and that its inclusion does not conflict with existing configurations.
buildArgs: -s clr.alljits+clr.alljitscommunity+clr.spmi -c $(_BuildConfig)
|
Tagging subscribers to this area: @hoyosjs |
BruceForstall
approved these changes
Apr 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
clr.alljitcommunitysubset is currently not built in the CI and it frequently breaks on Windows because development of riscv64/loongarch64 is mainly taking place on Unix. Last week, it broke twice: #114062 and #114292. The breakages are mainly due to different analysis warning threshold between llvm and msvc toolchains (explicit casts etc.).This PR enables it in superpmi CI leg. As to the overhead, it is not too much: before
windows-x64 checkedtook 7m 5s, now it's 8m 2s. Also updated this pipeline to trigger when someone updates its yml configs.