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.

Sign up for GitHub

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

Jump to bottom

Spurious failures of Web tests on Windows #400

Closed
newpavlov opened this issue Feb 21, 2024 · 1 comment · Fixed by #486
Closed

Spurious failures of Web tests on Windows #400

newpavlov opened this issue Feb 21, 2024 · 1 comment · Fixed by #486
Labels
testing

Comments

@newpavlov
Copy link
Member

newpavlov commented Feb 21, 2024 •
edited
Loading

Web tests spuriously fail on Windows on Run wasm-pack test --headless --chrome --features=js,test-in-browser with the following message:

 driver status: exit code: 1
driver stdout:
    Starting ChromeDriver 121.0.6167.184 (057a8ae7deb3374d0f1b04b36304d236f0136188-refs/branch-heads/6167@{#1818}) on port 50916
    Only local connections are allowed.
    Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

Error: driver failed to bind port during startup
[2024-02-21T13:23:08Z ERROR tiny_http] Error accepting new client: A blocking operation was interrupted by a call to WSACancelBlockingCall. (os error 10004)

Similar errors also happen with Firefox and Edge.
@newpavlov newpavlov changed the title Spurious fails of Web tests on Windows Spurious failures of Web tests on Windows Feb 21, 2024
@newpavlov
Copy link
Member Author

As a workaround we have temporarily marked Web Windows tests as continue-on-error: true in #405.

@josephlr josephlr mentioned this issue Apr 5, 2024
Merged
@newpavlov newpavlov mentioned this issue Jun 19, 2024
Merged
josephlr pushed a commit that referenced this issue Jun 19, 2024
@newpavlov
Completely disable Web tests on Windows (#486)
baae5fc 
`continue-on-error` does not work as I was expecting. AFAIK GitHub
Action does not have a straightforward solution for optionally failing
jobs, see: actions/runner#2347

Closes #400
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Completely disable Web tests on Windows rust-random/getrandom
1 participant
@newpavlov