You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent Rand builds seem to be failing with this error:
$ cargo --list | egrep "^\s*web$" -q || cargo install cargo-web
$ cargo web test --target wasm32-unknown-unknown --nodejs --features=stdweb
warning: debug builds on the wasm32-unknown-unknown are currently totally broken
forcing a release build
Compiling <...>
Finished release [optimized] target(s) in 2m 39s
Garbage collecting "rand-dfadd5273a3b9286.wasm"...
Processing "rand-dfadd5273a3b9286.wasm"...
thread 'main' panicked at 'unsupported custom section: '.debug_info'', src/wasm_context.rs:646:25
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Recent Rand builds seem to be failing with this error:
(Example)
Any idea what's up? (It could be due to outdated versions of
cargo-web
installed in our CI cache due to avoiding the update, I suppose.)The text was updated successfully, but these errors were encountered: