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

ci: update wasmbrowsertest to a specific commit #514

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

igolaizola
Copy link
Contributor

Using latest wasn't getting the latest version of wasmbrowsertest, so we're now using a specific commit.

Current version was failing due to timeouts, so we're updating to latest commit to see if it fixes the issue.

Using latest wasn't getting the latest version of wasmbrowsertest, so
we're now using a specific commit.

Current version was failing due to timeouts, so we're updating to
latest commit to see if it fixes the issue.
@igolaizola
Copy link
Contributor Author

@igolaizola
Copy link
Contributor Author

This repo had a similar issue, and it looks like they fixed it by updating the version as well: hajimehoshi/ebiten#2982

@igolaizola
Copy link
Contributor Author

This problem looks like a flaky test, so I'm not entirely sure if this PR will actually fix the issue.

The CI for this PR (#509) has now passed, even though wasmbrowsertest has not been updated there.

Copy link
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

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

Weird, issue. Thanks for looking into it, I think it's good to lock down the version anyway, so let's hope this fixes it 🤞🏻

@mafredri mafredri merged commit d1468a7 into coder:master Jan 30, 2025
4 checks passed
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