Remove parallelism warning from 4.14+ #26585
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
Parallelism warning isn't helpful, as it's highly unlikely to be the problem (already removed elsewhere)
"should not" as in "I don't think it will" or "should not" as in "wouldn't it be nice if opam didn't"? I.e., should we open an issue on |
it will not: https://github.com/ocaml/opam/blob/b9e808bf2aa91e6afca144f46e8547a291c20452/src/format/opamFile.ml#L3597 |
|
Thanks |
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.
While clearing the decks for something more important, these diffs were irritating.
The parallelism warning has been mostly removed (note that several of the +options packages from recent releases do not include it). It's highly unlikely to be the root cause, and the suggestion just causes the poor user to waste time and energy on a sequential build.
While here, there are three trivial updates to
+trunkpackages when building on MSYS2.Changes to
post-messagesshould not trigger rebuilds 🤞