Downgrade MSYS2 runtime to v3.5.4 #89
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 current version, v3.5.5, suffers from many a problem, two having seen fixes (a mis-handling of __SIGFLUSHFAST, the other a mis-handling of the X_OK flag when running as administrator) and at least one more that causes inexplicable hangs in Git's test suite. It is too late in the Git for Windows v2.48.0 cycle to investigate these problems thoroughly and flesh out fixes, therefore the only remaining option is to downgrade to the last known-okay MSYS2 runtime. Signed-off-by: Johannes Schindelin <[email protected]>
It has been overridden with a version that does not hang Git's test suite
This reverts commit 93b046f, as its job is now done. Signed-off-by: Johannes Schindelin <[email protected]>
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 upgrade to v3.5.5 was sadly premature: It is riddled with bugs, and the fixes did not come in fast enough in time for Git for Windows v2.48.0 (there are still some remaining unexplained hangs in Git's test suite, and I am unwilling to spend more of my vacation time on investigating them).