-
Notifications
You must be signed in to change notification settings - Fork 1.2k
ci: Update targets in verify-build #4780
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
Merged
Merged
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
fc54ea2 to
4da3ab1
Compare
88ba141 to
254586d
Compare
Do a few things: * Update the list to reflect current target tiers. * Add some missing T2 targets (includes ohos and gnullvm). * Remove unneeded `dist = False` and minimum toolchain config. * Delete some `-none-` targets, which don't make use of libc. * Add a check for duplicates. * Re-group and sort the lists.
Most of the targets are cross compiled anyway, and there isn't any advantage to running on native platforms. Start running everything on Linux which is the fastest and cheapest runner. As part of this, introduce a way to run only half of the target list from a single invocation. This is used to split the nightly job in two, each now only taking about as long as the stable job.
We have occasional CI failures on Windows where the environment variables don't get set so the artifact upload fails. Looking at the logs, it doesn't even appear the create-artifact job ran (but there are no errors). The Windows runners sometimes have trouble launching python scripts via `./`, so switch to using the python3 executable in hopes that this helps.
254586d to
6bb706b
Compare
Collaborator
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
67ad590 to
1789484
Compare
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
Do a few things: * Update the list to reflect current target tiers. * Add some missing T2 targets (includes ohos and gnullvm). * Remove unneeded `dist = False` and minimum toolchain config. * Delete some `-none-` targets, which don't make use of libc. * Add a check for duplicates. * Re-group and sort the lists. (backport <rust-lang#4780>) (cherry picked from commit 24d0049)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
Most of the targets are cross compiled anyway, and there isn't any advantage to running on native platforms. Start running everything on Linux which is the fastest and cheapest runner. As part of this, introduce a way to run only half of the target list from a single invocation. This is used to split the nightly job in two, each now only taking about as long as the stable job. (backport <rust-lang#4780>) (cherry picked from commit 56b916d)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit 5e95452)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
We have occasional CI failures on Windows where the environment variables don't get set so the artifact upload fails. Looking at the logs, it doesn't even appear the create-artifact job ran (but there are no errors). The Windows runners sometimes have trouble launching python scripts via `./`, so switch to using the python3 executable in hopes that this helps. (backport <rust-lang#4780>) (cherry picked from commit 962b985)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit c819173)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit a53f4bc)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
Do a few things: * Update the list to reflect current target tiers. * Add some missing T2 targets (includes ohos and gnullvm). * Remove unneeded `dist = False` and minimum toolchain config. * Delete some `-none-` targets, which don't make use of libc. * Add a check for duplicates. * Re-group and sort the lists. (backport <rust-lang#4780>) (cherry picked from commit 24d0049)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
Most of the targets are cross compiled anyway, and there isn't any advantage to running on native platforms. Start running everything on Linux which is the fastest and cheapest runner. As part of this, introduce a way to run only half of the target list from a single invocation. This is used to split the nightly job in two, each now only taking about as long as the stable job. (backport <rust-lang#4780>) (cherry picked from commit 56b916d)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit 5e95452)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
We have occasional CI failures on Windows where the environment variables don't get set so the artifact upload fails. Looking at the logs, it doesn't even appear the create-artifact job ran (but there are no errors). The Windows runners sometimes have trouble launching python scripts via `./`, so switch to using the python3 executable in hopes that this helps. (backport <rust-lang#4780>) (cherry picked from commit 962b985)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit c819173)
tgross35
added a commit
to tgross35/rust-libc
that referenced
this pull request
Nov 4, 2025
(backport <rust-lang#4780>) (cherry picked from commit a53f4bc)
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 4, 2025
Do a few things: * Update the list to reflect current target tiers. * Add some missing T2 targets (includes ohos and gnullvm). * Remove unneeded `dist = False` and minimum toolchain config. * Delete some `-none-` targets, which don't make use of libc. * Add a check for duplicates. * Re-group and sort the lists. (backport <#4780>) (cherry picked from commit 24d0049)
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 4, 2025
Most of the targets are cross compiled anyway, and there isn't any advantage to running on native platforms. Start running everything on Linux which is the fastest and cheapest runner. As part of this, introduce a way to run only half of the target list from a single invocation. This is used to split the nightly job in two, each now only taking about as long as the stable job. (backport <#4780>) (cherry picked from commit 56b916d)
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 4, 2025
We have occasional CI failures on Windows where the environment variables don't get set so the artifact upload fails. Looking at the logs, it doesn't even appear the create-artifact job ran (but there are no errors). The Windows runners sometimes have trouble launching python scripts via `./`, so switch to using the python3 executable in hopes that this helps. (backport <#4780>) (cherry picked from commit 962b985)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-CI
Area: CI-related items
O-powerpc
O-unix
stable-applied
This PR has been cherry-picked to libc's stable release branch
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.
Update the target list, switch to single-host build checks, and split the nightly build verification job into two.
More details are in the commit messages.