ci/android: use --locked when installing nextest - #10467
Merged
Merged
Conversation
|
GNU testsuite comparison: |
Contributor
|
It seems there is prebuilt of |
Contributor
Author
|
@oech3 I don't know, it's probably because until recently we also run the tests on Android x86. There is the following comment in |
Contributor
|
Yes. I considered siwtching to arm to avoid it. |
Contributor
|
I just tried |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The Android job in the CI currently fails with a compilation error (see, for example, https://github.com/uutils/coreutils/actions/runs/21314048084/job/61358741807?pr=10464#step:11:3573) after
nextestwas updated:The issue has already been reported and fixed upstream (nextest-rs/nextest#2990), though the maintainer recommends to use
--locked(nextest-rs/nextest#2990 (comment)).