From 820107d15e6ffbfb0f7257653f8889cb8f2dc452 Mon Sep 17 00:00:00 2001 From: David Tolnay Date: Sat, 10 Nov 2018 20:06:11 -0800 Subject: [PATCH] Move emscripten CI to allow_failures Not sure what is going on with this failure that just started happening with no code change on our end. Wait and see if it goes away. On asmjs-unknown-emscripten: Assertion failed: compiled without a main, but one is present. if you added it from JS, use Module["onRuntimeInitialized"] undefined:109 throw ex; ^ abort("Assertion failed: compiled without a main, but one is present. if you added it from JS, use Module[\"onRuntimeInitialized\"]") at Error On wasm32-unknown-emscripten: Assertion failed: compiled without a main, but one is present. if you added it from JS, use Module["onRuntimeInitialized"] failed to asynchronously prepare wasm: abort("Assertion failed: compiled without a main, but one is present. if you added it from JS, use Module[\"onRuntimeInitialized\"]") at Error --- .travis.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.travis.yml b/.travis.yml index 9dbbb33d..ad332f17 100644 --- a/.travis.yml +++ b/.travis.yml @@ -84,6 +84,8 @@ matrix: - cargo web test --target=wasm32-unknown-emscripten --nodejs allow_failures: + - rust: nightly + env: EMSCRIPTEN - rust: nightly env: CLIPPY