Strip whitespace to pacify test workflow #5
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
|
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.
In the upstream repo (manna-harbour/miryoku_babel), the test workflow succeeded the last time it ran (on ce22dc5: https://github.com/manna-harbour/miryoku_babel/actions/runs/3636723534) but in my fork, it failed on the exact same commit, because of whitespace differences: https://github.com/jablko/miryoku_babel/actions/runs/6101254887/job/16557227170#step:9:56
I haven't dug into why it succeeded in the upstream repo or the last time it ran. I think the whitespace got introduced in 45bfb70#diff-7eafe228ddeb8e53e4c3b64b4ce1696b8127915a5720da227f9393e63cb2d47eR1150. This change, which just adds/edits
results.rstrip()to eliminate that whitespace, makes the test workflow succeed.