fix: solo5 declares x-ci-accept-failures twice #28865
Open
+3
−6
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
Contributor
Author
|
Not sure what's going on with the CI errors, but they are all timeouts triggered hours after the job completion (:D !) |
hannesm
added a commit
to hannesm/solo5
that referenced
this pull request
Nov 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 following solo5 packages have duplicate entries for
x-ci-accept-failures(and are the only packages with duplicate fields definition!). This causesopam2jsonto error, which could be fixed with tweag/opam2json#3, but it's probably easier to just fix these package definitions to avoid the ambiguity. Note thatopam show --rawonly keeps the latest entry instead of the concatenation suggested here. cc @dinosaure