Conversation
Signed-off-by: David Thompson <davthomp@redhat.com>
Contributor
Author
|
I still can't replicate the failure locally, but it seems legit given it's failing consistently on GitHub Actions. I might have to push off releasing vscode-yaml until tomorrow. |
Contributor
Author
|
I figured out the problem as soon as I shut my laptop lid last night 🤦 just tested this morning and I can replicate the failure. |
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
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.
What does this PR do?
The unit tests seem to be failing when attempting to release, but I haven't been able to replicate it locally. Opening this to see if the CI workflow also replicates the unit test failure.
What issues does this PR fix or reference?
Is it tested? How?