search

rust-lang / portable-simd

The testing ground for the future of portable SIMD in Rust
Apache License 2.0
871 stars 78 forks source link

Spurious failures with Chrome wasm tests #68

Open workingjubilee opened 3 years ago

workingjubilee commented 3 years ago

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.

workingjubilee commented 3 years ago

With #72 merged, our CI time for wasm testing has ballooned to north of 15 minutes, from a relatively compact 5 minutes or so... it was still one of the slowest, but now it's really bad. Even pure time improvements on wasm testing are also welcome. Also note that non-SIMD scalar fallback testing obviously takes longer... actually an entire 10 minutes longer now, so it's around 25 minutes.