-
Notifications
You must be signed in to change notification settings - Fork 3
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
Restore windows CI #816
Restore windows CI #816
Conversation
Fixed the Pipelines test on Windows! Was making this too complicated by adding an As for the DevTests failure, I'm still not sure what's going on there... |
Incredible - admirable persistence on this issue! What do you think about disabling dev tests for Windows on this PR and continuing debugging for that on yet another follow-up? |
env: | ||
GIN_DATA_DIRECTORY: ${{ github.workspace }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohhh, I had no idea these were (or could be) scoped per line under run
/steps
Sure sounds good to me. |
Cool - this PR technically needs your approval since I'm the one who opened it yesterday 😆 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. Looks good!
Restoring the previous state of attempting to fix Windows pipelines
There also seems to be a new failure in the Windows DevTests suite (but never BuildTests) following merge of #786
At time of merge it was only seen in the LiveServices tests (and thus disregarded as an impersistent live service specific problem) and not in the dev tests; but it's been seen in the DevTests for Windows ever since as well