Fix qemu setup using too new curl options #313
Merged
Conversation
This file contains 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
The build failed in driver ARM build due to the usage of `--retry-all-errors`. The build on master also failed, because we don't use this option on `ubuntu20.04`. I think we'll need to add a manual retry loop there as a crutch for old systems with old curl. As for now I'll move the `v0`, `v0.4` and `v0.4.0` to this new commit and this will trigger the "release-on-tag" workflow again
Veetaha
changed the title
Veetaha
changed the title
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.
The build failed in driver ARM build due to the usage of
--retry-all-errors.The build on master also failed, because we don't use this option on
ubuntu20.04. I think we'll need to add a manual retry loop there as a crutch for old systems with old curl.As for now I'll move the
v0,v0.4andv0.4.0tags manually to this new commit in ahotfix/0.4branch and this will trigger the "release-on-tag" workflow again and it should update the GH release 🤞