rust-lang / rust-lang/portable-simd
Spurious failures with Chrome wasm tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 108
- Avg merge
- 22h 53m
- Merged PRs (30d)
- 3
Description
Currently in CI we have a periodic failure to connect to our headless Chrome on port 99 in order to do Wasm SIMD testing. Obviously this puts a bit of a crimp in our style with respect to such tests! It might be preferable to use an alternative wasm runtime, perhaps by using the wasmtime crate embedded in Rust, with wasm_simd enabled. @KodrAus has expressed in an interest in addressing this (and thank you!), but I figured I'd actually open the issue so we can keep track of any interesting details we find about the failures until it's fixed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the CI setup for headless Chrome on port 99 and the Wasm SIMD test invocation, then review the linked wasmtime example and wasm_simd configuration. Done means the CI no longer has periodic connection failures and the Wasm SIMD tests pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100