We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Cloning the repository and running cargo test results in the following test failures:
cargo test
failures: build::build_crates_with_same_names build::build_different_profiles build::build_force build::build_from_new build::build_no_install build::build_with_and_without_wasm_bindgen_debug build::build_with_arbitrary_cargo_options build::dash_dash_web_target_has_error_on_old_bindgen build::it_should_build_crates_in_a_workspace build::it_should_build_js_hello_world_example build::it_should_build_nested_project_with_transitive_dependencies build::renamed_crate_name_works log_level::log_level_error log_level::log_level_info log_level::log_level_warn log_level::quiet manifest::parse_crate_data_returns_unused_keys_in_cargo_toml test::cdylib_not_required test::complains_about_missing_wasm_bindgen_test_dependency test::extra_options_is_passed_to_cargo_when_building_tests test::it_can_find_a_webdriver_on_path test::it_can_run_browser_tests test::it_can_run_failing_tests test::it_can_run_node_tests test::it_can_run_tests_with_different_wbg_test_and_wbg_versions test::it_requires_node_or_a_browser test::renamed_crate_name_works test::test_output_is_printed_once_in_both_stdout_and_failures test::the_headless_flag_requires_a_browser wasm_opt::custom_args wasm_opt::disable_in_release wasm_opt::enable_in_dev wasm_opt::misconfigured wasm_opt::off_in_dev wasm_opt::on_in_release
The same can also be observed in the CI for the master branch.
Half of these apparently are due to some Once instance has previously been poisoned errors while the other half are apparently due to:
Once instance has previously been poisoned
Error: failed to download from https://github.com/WebAssembly/binaryen/releases/download/version_108/binaryen-version_108-x86-linux.tar.gz
The text was updated successfully, but these errors were encountered:
wasm-pack build
wasm-pack test
Fixed in #1188
Sorry, something went wrong.
No branches or pull requests
Cloning the repository and running
cargo test
results in the following test failures:The same can also be observed in the CI for the master branch.
Half of these apparently are due to some
Once instance has previously been poisoned
errors while the other half are apparently due to:The text was updated successfully, but these errors were encountered: