Skip to content

Try using windows-latest CI#4553

Merged
alexcrichton merged 1 commit intobytecodealliance:mainfrom
alexcrichton:windows-latest
Jul 29, 2022
Merged

Try using windows-latest CI#4553
alexcrichton merged 1 commit intobytecodealliance:mainfrom
alexcrichton:windows-latest

Conversation

@alexcrichton
Copy link
Copy Markdown
Member

See if our windows-2019 woes are solved now that backtraces are using
frame pointers instead of native APIs.

@alexcrichton alexcrichton marked this pull request as ready for review July 29, 2022 14:10
See if our `windows-2019` woes are solved now that backtraces are using
frame pointers instead of native APIs.
@alexcrichton
Copy link
Copy Markdown
Member Author

Ok looks like things are indeed green now!

Due to our repository configuration this can't land immediately though. The CI gates we're requiring have "windows-2019" in the name whereas in this PR they switched to "windows-latest". To land this I'll need to switch the gates to the "windows-latest" version as reported in this PR. When I do that switch though all other PRs will have to rebase on this to merge since they otherwise won't have a run on "windows-latest" to succeed.

@alexcrichton alexcrichton requested a review from fitzgen July 29, 2022 15:26
Copy link
Copy Markdown
Member

@cfallin cfallin left a comment

Choose a reason for hiding this comment

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

Thanks for this! Happy to finally see this perplexing bug disappear...

@alexcrichton alexcrichton merged commit b127354 into bytecodealliance:main Jul 29, 2022
@alexcrichton alexcrichton deleted the windows-latest branch July 29, 2022 17:15
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