Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to fix allowed test failure on Windows #1232

Merged
merged 2 commits into from
Jul 9, 2021
Merged

Conversation

atomb
Copy link
Contributor

@atomb atomb commented Jul 8, 2021

No description provided.

@atomb atomb requested a review from kquick July 8, 2021 22:15
They seem to hang instead of failing at the moment, so until we get them
working it seems like it's better to just leave them out.
Copy link
Member

@kquick kquick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not clear what's wrong with the windows CI builds, but it also doesn't seem to be related to the code or the CI configs, so I agree that disabling them for now to get green CI is more useful.

Looks like the actual test failure is probably a transient network issue.

I'm not sure why the windows test is marked as "skipped" as opposed to just being gone; I'm slightly concerned that will result in yellow status instead of a green checkmark but maybe it's just a sync comparison between this PR and master that will go away when the merge happens.

@atomb
Copy link
Contributor Author

atomb commented Jul 9, 2021

Yeah, I just re-started the jobs in the hop that the failed test will work this time. 🤞

@atomb atomb merged commit 02aa441 into master Jul 9, 2021
@atomb atomb deleted the at-windows-fail branch July 9, 2021 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants