>>> wasm-pack: Building community/wasm-pack 0.14.0-r1 (using abuild 3.17.0_rc2-r0) started Wed, 06 May 2026 07:37:53 +0000 >>> wasm-pack: Validating /home/buildozer/aports/community/wasm-pack/APKBUILD... >>> wasm-pack: Analyzing dependencies... >>> wasm-pack: Installing for build: build-base cargo rustc-dev rust-wasm bzip2-dev cargo-auditable cmake curl-dev openssl-dev>3 samurai wasi-sdk zstd-dev binaryen cargo-generate nodejs wasm-bindgen ( 1/50) Installing libffi (3.5.2-r1) ( 2/50) Installing xz-libs (5.8.3-r0) ( 3/50) Installing libxml2 (2.13.9-r1) ( 4/50) Installing llvm22-libs (22.1.3-r0) ( 5/50) Installing scudo-malloc (22.1.3-r0) ( 6/50) Installing rust (1.95.0-r0) ( 7/50) Installing sqlite-libs (3.53.0-r0) ( 8/50) Installing cargo (1.95.0-r0) ( 9/50) Installing rustc-dev (1.95.0-r0) (10/50) Installing lld22-libs (22.1.3-r0) (11/50) Installing lld22 (22.1.3-r0) (12/50) Installing wasi-libc (0.20250204-r1) (13/50) Installing rust-wasm (1.95.0-r0) (14/50) Installing libbz2 (1.0.8-r6) (15/50) Installing bzip2-dev (1.0.8-r6) (16/50) Installing cargo-auditable (0.7.4-r0) (17/50) Installing libarchive (3.8.7-r0) (18/50) Installing rhash-libs (1.4.6-r0) (19/50) Installing libuv (1.52.1-r0) (20/50) Installing cmake (4.2.3-r0) (21/50) Installing brotli (1.2.0-r1) (22/50) Installing brotli-dev (1.2.0-r1) (23/50) Installing c-ares-dev (1.34.6-r0) (24/50) Installing libidn2-dev (2.3.8-r0) (25/50) Installing libpsl-utils (0.21.5-r3) (26/50) Installing libpsl-dev (0.21.5-r3) (27/50) Installing nghttp2-dev (1.69.0-r0) (28/50) Installing openssl-dev (3.5.6-r0) (29/50) Installing zlib-dev (1.3.2-r0) (30/50) Installing zstd (1.5.7-r2) (31/50) Installing zstd-dev (1.5.7-r2) (32/50) Installing curl-dev (8.20.0-r0) (33/50) Installing samurai (1.2-r8) (34/50) Installing wasi-libcxx (22.1.3-r0) (35/50) Installing wasi-compiler-rt (22.1.3-r0) (36/50) Installing wasi-sdk (27-r1) (37/50) Installing binaryen (123-r1) (38/50) Installing llhttp (9.3.1-r0) (39/50) Installing libssh2 (1.11.1-r1) (40/50) Installing libgit2 (1.9.3-r0) (41/50) Installing cargo-generate (0.23.8-r0) (42/50) Installing ca-certificates (20260413-r0) (43/50) Installing ada-libs (3.3.0-r0) (44/50) Installing icu-data-en (78.1-r0) Executing icu-data-en-78.1-r0.post-install * If you need ICU with non-English locales and legacy charset support, install * package icu-data-full. (45/50) Installing icu-libs (78.1-r0) (46/50) Installing simdjson (4.2.4-r0) (47/50) Installing simdutf (9.0.0-r0) (48/50) Installing nodejs (24.14.1-r1) (49/50) Installing wasm-bindgen (0.2.118-r0) (50/50) Installing .makedepends-wasm-pack (20260506.073800) Executing busybox-1.37.0-r31.trigger Executing ca-certificates-20260413-r0.trigger OK: 1726.0 MiB in 153 packages >>> wasm-pack: Cleaning up srcdir >>> wasm-pack: Cleaning up pkgdir >>> wasm-pack: Cleaning up tmpdir >>> wasm-pack: Fetching https://distfiles.alpinelinux.org/distfiles/v3.24/wasm-pack-v0.14.0.tar.gz /var/cache/distfiles/v3.24/wasm-pack-v0.14.0.tar.gz: OK /home/buildozer/aports/community/wasm-pack/any-version.patch: OK /home/buildozer/aports/community/wasm-pack/musl.patch: OK /home/buildozer/aports/community/wasm-pack/upgrade-binary-install.patch: OK /home/buildozer/aports/community/wasm-pack/wasm-bindgen-ver.patch: OK >>> wasm-pack: Fetching https://distfiles.alpinelinux.org/distfiles/v3.24/wasm-pack-v0.14.0.tar.gz /var/cache/distfiles/v3.24/wasm-pack-v0.14.0.tar.gz: OK /home/buildozer/aports/community/wasm-pack/any-version.patch: OK /home/buildozer/aports/community/wasm-pack/musl.patch: OK /home/buildozer/aports/community/wasm-pack/upgrade-binary-install.patch: OK /home/buildozer/aports/community/wasm-pack/wasm-bindgen-ver.patch: OK >>> wasm-pack: Unpacking /var/cache/distfiles/v3.24/wasm-pack-v0.14.0.tar.gz... >>> wasm-pack: any-version.patch patching file src/install/mod.rs >>> wasm-pack: musl.patch patching file tests/all/test.rs >>> wasm-pack: upgrade-binary-install.patch patching file Cargo.lock patching file Cargo.toml >>> wasm-pack: wasm-bindgen-ver.patch patching file tests/all/lockfile.rs patching file tests/all/readme.rs patching file tests/all/utils/fixture.rs patching file tests/all/download.rs Updating crates.io index Updating git repository `https://github.com/drager/binary-install` Downloading crates ... Downloaded zeroize_derive v1.4.3 Downloaded errno v0.3.14 Downloaded futures-core v0.3.31 Downloaded which v8.0.0 Downloaded same-file v1.0.6 Downloaded siphasher v1.0.1 Downloaded walkdir v2.5.0 Downloaded futures-executor v0.3.31 Downloaded unicode-ident v1.0.22 Downloaded pin-project-lite v0.2.16 Downloaded wait-timeout v0.2.1 Downloaded rustc-demangle v0.1.27 Downloaded jobserver v0.1.34 Downloaded byteorder v1.5.0 Downloaded tinystr v0.8.2 Downloaded writeable v0.6.2 Downloaded displaydoc v0.2.5 Downloaded zerovec-derive v0.11.2 Downloaded zerofrom v0.1.6 Downloaded webpki-roots v0.26.11 Downloaded zerofrom-derive v0.1.6 Downloaded serde_spanned v1.0.4 Downloaded heck v0.5.0 Downloaded termtree v0.5.1 Downloaded synstructure v0.13.2 Downloaded quote v1.0.43 Downloaded slab v0.4.11 Downloaded path-clean v1.0.1 Downloaded anstyle-query v1.1.5 Downloaded crypto-common v0.1.7 Downloaded parking_lot v0.12.5 Downloaded tempfile v3.24.0 Downloaded icu_provider v2.1.1 Downloaded utf8parse v0.2.2 Downloaded parking_lot_core v0.9.12 Downloaded toml_parser v1.0.6+spec-1.1.0 Downloaded difflib v0.4.0 Downloaded getrandom v0.3.4 Downloaded is_executable v1.0.5 Downloaded indexmap v2.13.0 Downloaded zerovec v0.11.5 Downloaded time-core v0.1.7 Downloaded serde_json v1.0.149 Downloaded block-buffer v0.10.4 Downloaded version_check v0.9.5 Downloaded winnow v0.7.14 Downloaded dirs-next v2.0.0 Downloaded webpki-roots v1.0.5 Downloaded crc v3.4.0 Downloaded float-cmp v0.10.0 Downloaded xattr v1.6.1 Downloaded cpufeatures v0.2.17 Downloaded constant_time_eq v0.3.1 Downloaded bstr v1.12.1 Downloaded predicates-tree v1.0.12 Downloaded rustls v0.23.36 Downloaded crc-catalog v2.4.0 Downloaded env_filter v0.1.4 Downloaded dirs-sys-next v0.1.2 Downloaded hex v0.4.3 Downloaded num-conv v0.1.0 Downloaded powerfmt v0.2.0 Downloaded rustix v1.1.3 Downloaded inout v0.1.4 Downloaded predicates v3.1.3 Downloaded env_logger v0.11.8 Downloaded libc v0.2.180 Downloaded anstream v0.6.21 Downloaded anstyle-parse v0.2.7 Downloaded anstyle v1.0.13 Downloaded predicates-core v1.0.9 Downloaded shell-words v1.1.1 Downloaded lazy_static v1.5.0 Downloaded syn v2.0.114 Downloaded cipher v0.4.4 Downloaded generic-array v0.14.7 Downloaded fs4 v0.13.1 Downloaded sha1 v0.10.6 Downloaded deranged v0.5.5 Downloaded zlib-rs v0.5.5 Downloaded assert_cmd v2.1.2 Downloaded zstd v0.13.3 Downloaded human-panic v2.0.6 Downloaded semver v1.0.27 Downloaded cargo_metadata v0.23.1 Downloaded icu_properties_data v2.1.2 Downloaded filetime v0.2.27 Downloaded sha2 v0.10.9 Downloaded digest v0.10.7 Downloaded thiserror-impl v2.0.18 Downloaded thiserror v2.0.18 Downloaded dialoguer v0.12.0 Downloaded camino v1.2.2 Downloaded ppmd-rust v1.3.0 Downloaded autocfg v1.5.0 Downloaded futures-util v0.3.31 Downloaded clap_derive v4.5.49 Downloaded idna v1.1.0 Downloaded cargo-platform v0.3.2 Downloaded scc v2.4.0 Downloaded console v0.16.2 Downloaded hashbrown v0.16.1 Downloaded deflate64 v0.1.10 Downloaded hmac v0.12.1 Downloaded zstd-safe v7.2.4 Downloaded iana-time-zone v0.1.64 Downloaded addr2line v0.25.1 Downloaded ureq v2.12.1 Downloaded base64 v0.22.1 Downloaded anyhow v1.0.100 Downloaded num-traits v0.2.19 Downloaded zerotrie v0.2.3 Downloaded serde v1.0.228 Downloaded url v2.5.8 Downloaded libbz2-rs-sys v0.2.2 Downloaded ring v0.17.14 Downloaded tar v0.4.44 Downloaded bzip2 v0.6.1 Downloaded typenum v1.19.0 Downloaded clap v4.5.54 Downloaded uuid v1.19.0 Downloaded zopfli v0.8.3 Downloaded pbkdf2 v0.12.2 Downloaded pkg-config v0.3.32 Downloaded clap_lex v0.7.7 Downloaded miniz_oxide v0.8.9 Downloaded flate2 v1.1.8 Downloaded backtrace v0.3.76 Downloaded cc v1.2.53 Downloaded rustls-webpki v0.103.9 Downloaded memchr v2.7.6 Downloaded icu_normalizer_data v2.1.1 Downloaded icu_collections v2.1.1 Downloaded icu_locale_core v2.1.1 Downloaded proc-macro2 v1.0.105 Downloaded toml v0.9.11+spec-1.1.0 Downloaded log v0.4.29 Downloaded bumpalo v3.19.1 Downloaded find-msvc-tools v0.1.8 Downloaded icu_normalizer v2.1.1 Downloaded icu_properties v2.1.2 Downloaded regex-syntax v0.8.8 Downloaded serde_core v1.0.228 Downloaded serde_derive v1.0.228 Downloaded crc32fast v1.5.0 Downloaded toml_datetime v0.7.5+spec-1.1.0 Downloaded once_cell v1.21.3 Downloaded toml_writer v1.0.6+spec-1.1.0 Downloaded aes v0.8.4 Downloaded itoa v1.0.17 Downloaded zeroize v1.8.2 Downloaded smallvec v1.15.1 Downloaded rustls-pki-types v1.14.0 Downloaded serde_ignored v0.1.14 Downloaded zip v6.0.0 Downloaded lock_api v0.4.14 Downloaded fastrand v2.3.0 Downloaded simd-adler32 v0.3.8 Downloaded shlex v1.3.0 Downloaded getrandom v0.2.17 Downloaded litemap v0.8.1 Downloaded yoke v0.8.1 Downloaded colorchoice v1.0.4 Downloaded is_terminal_polyfill v1.70.2 Downloaded normalize-line-endings v0.3.0 Downloaded sdd v3.0.10 Downloaded serial_test_derive v3.3.1 Downloaded adler2 v2.0.1 Downloaded zmij v1.0.16 Downloaded form_urlencoded v1.2.2 Downloaded yoke-derive v0.8.1 Downloaded percent-encoding v2.3.2 Downloaded env_home v0.1.0 Downloaded glob v0.3.3 Downloaded pin-utils v0.1.0 Downloaded regex v1.12.2 Downloaded aho-corasick v1.1.4 Downloaded serial_test v3.3.1 Downloaded strsim v0.11.1 Downloaded linux-raw-sys v0.11.0 Downloaded cfg-if v1.0.4 Downloaded time v0.3.45 Downloaded clap_builder v4.5.54 Downloaded subtle v2.6.1 Downloaded sysinfo v0.37.2 Downloaded chrono v0.4.43 Downloaded gimli v0.32.3 Downloaded lzma-rust2 v0.13.0 Downloaded idna_adapter v1.2.1 Downloaded unicode-width v0.2.2 Downloaded utf8_iter v1.0.4 Downloaded scopeguard v1.2.0 Downloaded equivalent v1.0.2 Downloaded untrusted v0.9.0 Downloaded socks v0.3.4 Downloaded potential_utf v0.1.4 Downloaded stable_deref_trait v1.2.1 Downloaded bitflags v2.10.0 Downloaded futures-task v0.3.31 Downloaded object v0.37.3 Downloaded regex-automata v0.4.13 Downloaded zstd-sys v2.0.16+zstd.1.5.7 Compiling proc-macro2 v1.0.105 Compiling quote v1.0.43 Compiling unicode-ident v1.0.22 Compiling libc v0.2.180 Compiling cfg-if v1.0.4 Compiling version_check v0.9.5 Compiling typenum v1.19.0 Compiling serde_core v1.0.228 Compiling stable_deref_trait v1.2.1 Compiling subtle v2.6.1 Compiling litemap v0.8.1 Compiling memchr v2.7.6 Compiling writeable v0.6.2 Compiling find-msvc-tools v0.1.8 Compiling rustix v1.1.3 Compiling shlex v1.3.0 Compiling icu_normalizer_data v2.1.1 Compiling smallvec v1.15.1 Compiling icu_properties_data v2.1.2 Compiling bitflags v2.10.0 Compiling getrandom v0.3.4 Compiling linux-raw-sys v0.11.0 Compiling simd-adler32 v0.3.8 Compiling crc32fast v1.5.0 Compiling adler2 v2.0.1 Compiling log v0.4.29 Compiling once_cell v1.21.3 Compiling zmij v1.0.16 Compiling serde v1.0.228 Compiling zstd-sys v2.0.16+zstd.1.5.7 Compiling utf8parse v0.2.2 Compiling serde_json v1.0.149 Compiling untrusted v0.9.0 Compiling zstd-safe v7.2.4 Compiling itoa v1.0.17 Compiling anstyle-query v1.1.5 Compiling colorchoice v1.0.4 Compiling anstyle v1.0.13 Compiling is_terminal_polyfill v1.70.2 Compiling powerfmt v0.2.0 Compiling zlib-rs v0.5.5 Compiling rustls v0.23.36 Compiling percent-encoding v2.3.2 Compiling autocfg v1.5.0 Compiling utf8_iter v1.0.4 Compiling crc-catalog v2.4.0 Compiling object v0.37.3 Compiling num-conv v0.1.0 Compiling camino v1.2.2 Compiling byteorder v1.5.0 Compiling time-core v0.1.7 Compiling parking_lot_core v0.9.12 Compiling hashbrown v0.16.1 Compiling bumpalo v3.19.1 Compiling anyhow v1.0.100 Compiling winnow v0.7.14 Compiling gimli v0.32.3 Compiling equivalent v1.0.2 Compiling thiserror v2.0.18 Compiling libbz2-rs-sys v0.2.2 Compiling scopeguard v1.2.0 Compiling deflate64 v0.1.10 Compiling strsim v0.11.1 Compiling constant_time_eq v0.3.1 Compiling base64 v0.22.1 Compiling ppmd-rust v1.3.0 Compiling toml_writer v1.0.6+spec-1.1.0 Compiling fastrand v2.3.0 Compiling heck v0.5.0 Compiling clap_lex v0.7.7 Compiling unicode-width v0.2.2 Compiling rustc-demangle v0.1.27 Compiling siphasher v1.0.1 Compiling is_executable v1.0.5 Compiling same-file v1.0.6 Compiling hex v0.4.3 Compiling shell-words v1.1.1 Compiling iana-time-zone v0.1.64 Compiling env_home v0.1.0 Compiling glob v0.3.3 Compiling path-clean v1.0.1 Compiling anstyle-parse v0.2.7 Compiling crc v3.4.0 Compiling lock_api v0.4.14 Compiling miniz_oxide v0.8.9 Compiling form_urlencoded v1.2.2 Compiling walkdir v2.5.0 Compiling deranged v0.5.5 Compiling env_filter v0.1.4 Compiling anstream v0.6.21 Compiling generic-array v0.14.7 Compiling env_logger v0.11.8 Compiling zstd v0.13.3 Compiling num-traits v0.2.19 Compiling zopfli v0.8.3 Compiling clap_builder v4.5.54 Compiling bzip2 v0.6.1 Compiling indexmap v2.13.0 Compiling syn v2.0.114 Compiling jobserver v0.1.34 Compiling chrono v0.4.43 Compiling cpufeatures v0.2.17 Compiling getrandom v0.2.17 Compiling dirs-sys-next v0.1.2 Compiling filetime v0.2.27 Compiling socks v0.3.4 Compiling console v0.16.2 Compiling sysinfo v0.37.2 Compiling cc v1.2.53 Compiling uuid v1.19.0 Compiling dirs-next v2.0.0 Compiling parking_lot v0.12.5 Compiling time v0.3.45 Compiling crypto-common v0.1.7 Compiling block-buffer v0.10.4 Compiling inout v0.1.4 Compiling cipher v0.4.4 Compiling digest v0.10.7 Compiling toml_parser v1.0.6+spec-1.1.0 Compiling hmac v0.12.1 Compiling sha2 v0.10.9 Compiling sha1 v0.10.6 Compiling aes v0.8.4 Compiling pbkdf2 v0.12.2 Compiling lzma-rust2 v0.13.0 Compiling xattr v1.6.1 Compiling tempfile v3.24.0 Compiling fs4 v0.13.1 Compiling which v8.0.0 Compiling tar v0.4.44 Compiling ring v0.17.14 Compiling addr2line v0.25.1 Compiling flate2 v1.1.8 Compiling serde_spanned v1.0.4 Compiling toml_datetime v0.7.5+spec-1.1.0 Compiling semver v1.0.27 Compiling cargo-platform v0.3.2 Compiling serde_ignored v0.1.14 Compiling toml v0.9.11+spec-1.1.0 Compiling backtrace v0.3.76 Compiling synstructure v0.13.2 Compiling zerofrom-derive v0.1.6 Compiling yoke-derive v0.8.1 Compiling zerovec-derive v0.11.2 Compiling displaydoc v0.2.5 Compiling zeroize_derive v1.4.3 Compiling serde_derive v1.0.228 Compiling thiserror-impl v2.0.18 Compiling clap_derive v4.5.49 Compiling zeroize v1.8.2 Compiling rustls-pki-types v1.14.0 Compiling zip v6.0.0 Compiling dialoguer v0.12.0 Compiling zerofrom v0.1.6 Compiling yoke v0.8.1 Compiling rustls-webpki v0.103.9 Compiling webpki-roots v1.0.5 Compiling webpki-roots v0.26.11 Compiling zerovec v0.11.5 Compiling zerotrie v0.2.3 Compiling clap v4.5.54 Compiling tinystr v0.8.2 Compiling potential_utf v0.1.4 Compiling icu_collections v2.1.1 Compiling icu_locale_core v2.1.1 Compiling icu_provider v2.1.1 Compiling icu_normalizer v2.1.1 Compiling icu_properties v2.1.2 Compiling cargo_metadata v0.23.1 Compiling human-panic v2.0.6 Compiling idna_adapter v1.2.1 Compiling idna v1.1.0 Compiling url v2.5.8 Compiling ureq v2.12.1 Compiling binary-install v0.5.0 (https://github.com/drager/binary-install?rev=3c307990be865f73fe6ad069e89de9d8f02d8b7e#3c307990) Compiling wasm-pack v0.14.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0) Finished `release` profile [optimized] target(s) in 1m 18s Compiling proc-macro2 v1.0.105 Compiling unicode-ident v1.0.22 Compiling quote v1.0.43 Compiling libc v0.2.180 Compiling cfg-if v1.0.4 Compiling typenum v1.19.0 Compiling version_check v0.9.5 Compiling memchr v2.7.6 Compiling serde_core v1.0.228 Compiling stable_deref_trait v1.2.1 Compiling subtle v2.6.1 Compiling smallvec v1.15.1 Compiling find-msvc-tools v0.1.8 Compiling shlex v1.3.0 Compiling litemap v0.8.1 Compiling writeable v0.6.2 Compiling rustix v1.1.3 Compiling icu_normalizer_data v2.1.1 Compiling linux-raw-sys v0.11.0 Compiling log v0.4.29 Compiling simd-adler32 v0.3.8 Compiling bitflags v2.10.0 Compiling getrandom v0.3.4 Compiling icu_properties_data v2.1.2 Compiling adler2 v2.0.1 Compiling crc32fast v1.5.0 Compiling once_cell v1.21.3 Compiling autocfg v1.5.0 Compiling zstd-sys v2.0.16+zstd.1.5.7 Compiling serde v1.0.228 Compiling zmij v1.0.16 Compiling anstyle v1.0.13 Compiling utf8parse v0.2.2 Compiling zstd-safe v7.2.4 Compiling untrusted v0.9.0 Compiling serde_json v1.0.149 Compiling anstyle-query v1.1.5 Compiling crc-catalog v2.4.0 Compiling colorchoice v1.0.4 Compiling parking_lot_core v0.9.12 Compiling percent-encoding v2.3.2 Compiling powerfmt v0.2.0 Compiling utf8_iter v1.0.4 Compiling itoa v1.0.17 Compiling rustls v0.23.36 Compiling zlib-rs v0.5.5 Compiling object v0.37.3 Compiling is_terminal_polyfill v1.70.2 Compiling anyhow v1.0.100 Compiling bumpalo v3.19.1 Compiling gimli v0.32.3 Compiling scopeguard v1.2.0 Compiling thiserror v2.0.18 Compiling time-core v0.1.7 Compiling regex-syntax v0.8.8 Compiling num-conv v0.1.0 Compiling equivalent v1.0.2 Compiling libbz2-rs-sys v0.2.2 Compiling winnow v0.7.14 Compiling hashbrown v0.16.1 Compiling byteorder v1.5.0 Compiling camino v1.2.2 Compiling deflate64 v0.1.10 Compiling base64 v0.22.1 Compiling clap_lex v0.7.7 Compiling rustc-demangle v0.1.27 Compiling fastrand v2.3.0 Compiling strsim v0.11.1 Compiling toml_writer v1.0.6+spec-1.1.0 Compiling heck v0.5.0 Compiling constant_time_eq v0.3.1 Compiling unicode-width v0.2.2 Compiling ppmd-rust v1.3.0 Compiling siphasher v1.0.1 Compiling pin-project-lite v0.2.16 Compiling pin-utils v0.1.0 Compiling env_home v0.1.0 Compiling predicates-core v1.0.9 Compiling shell-words v1.1.1 Compiling same-file v1.0.6 Compiling futures-task v0.3.31 Compiling futures-core v0.3.31 Compiling is_executable v1.0.5 Compiling anstyle-parse v0.2.7 Compiling crc v3.4.0 Compiling lock_api v0.4.14 Compiling hex v0.4.3 Compiling slab v0.4.11 Compiling iana-time-zone v0.1.64 Compiling sdd v3.0.10 Compiling path-clean v1.0.1 Compiling normalize-line-endings v0.3.0 Compiling miniz_oxide v0.8.9 Compiling form_urlencoded v1.2.2 Compiling difflib v0.4.0 Compiling glob v0.3.3 Compiling termtree v0.5.1 Compiling env_filter v0.1.4 Compiling assert_cmd v2.1.2 Compiling lazy_static v1.5.0 Compiling deranged v0.5.5 Compiling walkdir v2.5.0 Compiling predicates-tree v1.0.12 Compiling anstream v0.6.21 Compiling futures-util v0.3.31 Compiling generic-array v0.14.7 Compiling env_logger v0.11.8 Compiling num-traits v0.2.19 Compiling zopfli v0.8.3 Compiling zstd v0.13.3 Compiling scc v2.4.0 Compiling aho-corasick v1.1.4 Compiling clap_builder v4.5.54 Compiling bzip2 v0.6.1 Compiling indexmap v2.13.0 Compiling syn v2.0.114 Compiling float-cmp v0.10.0 Compiling chrono v0.4.43 Compiling jobserver v0.1.34 Compiling cpufeatures v0.2.17 Compiling getrandom v0.2.17 Compiling socks v0.3.4 Compiling filetime v0.2.27 Compiling dirs-sys-next v0.1.2 Compiling sysinfo v0.37.2 Compiling console v0.16.2 Compiling wait-timeout v0.2.1 Compiling dirs-next v2.0.0 Compiling uuid v1.19.0 Compiling parking_lot v0.12.5 Compiling cc v1.2.53 Compiling time v0.3.45 Compiling crypto-common v0.1.7 Compiling block-buffer v0.10.4 Compiling inout v0.1.4 Compiling cipher v0.4.4 Compiling digest v0.10.7 Compiling sha2 v0.10.9 Compiling hmac v0.12.1 Compiling sha1 v0.10.6 Compiling aes v0.8.4 Compiling toml_parser v1.0.6+spec-1.1.0 Compiling pbkdf2 v0.12.2 Compiling lzma-rust2 v0.13.0 Compiling regex-automata v0.4.13 Compiling xattr v1.6.1 Compiling tempfile v3.24.0 Compiling fs4 v0.13.1 Compiling which v8.0.0 Compiling tar v0.4.44 Compiling futures-executor v0.3.31 Compiling addr2line v0.25.1 Compiling ring v0.17.14 Compiling serde_spanned v1.0.4 Compiling toml_datetime v0.7.5+spec-1.1.0 Compiling semver v1.0.27 Compiling cargo-platform v0.3.2 Compiling serde_ignored v0.1.14 Compiling toml v0.9.11+spec-1.1.0 Compiling flate2 v1.1.8 Compiling backtrace v0.3.76 Compiling regex v1.12.2 Compiling bstr v1.12.1 Compiling synstructure v0.13.2 Compiling predicates v3.1.3 Compiling zerofrom-derive v0.1.6 Compiling yoke-derive v0.8.1 Compiling zerovec-derive v0.11.2 Compiling displaydoc v0.2.5 Compiling zeroize_derive v1.4.3 Compiling serde_derive v1.0.228 Compiling thiserror-impl v2.0.18 Compiling clap_derive v4.5.49 Compiling serial_test_derive v3.3.1 Compiling serial_test v3.3.1 Compiling zeroize v1.8.2 Compiling rustls-pki-types v1.14.0 Compiling zip v6.0.0 Compiling dialoguer v0.12.0 Compiling zerofrom v0.1.6 Compiling rustls-webpki v0.103.9 Compiling webpki-roots v1.0.5 Compiling yoke v0.8.1 Compiling webpki-roots v0.26.11 Compiling zerovec v0.11.5 Compiling zerotrie v0.2.3 Compiling clap v4.5.54 Compiling tinystr v0.8.2 Compiling potential_utf v0.1.4 Compiling icu_collections v2.1.1 Compiling icu_locale_core v2.1.1 Compiling icu_provider v2.1.1 Compiling icu_properties v2.1.2 Compiling icu_normalizer v2.1.1 Compiling human-panic v2.0.6 Compiling cargo_metadata v0.23.1 Compiling idna_adapter v1.2.1 Compiling idna v1.1.0 Compiling url v2.5.8 Compiling ureq v2.12.1 Compiling binary-install v0.5.0 (https://github.com/drager/binary-install?rev=3c307990be865f73fe6ad069e89de9d8f02d8b7e#3c307990) Compiling wasm-pack v0.14.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0) warning: unused import: `std::env` --> tests/all/test.rs:4:5 | 4 | use std::env; | ^^^^^^^^ | = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default warning: methods `install_local_geckodriver` and `install_local_chromedriver` are never used --> tests/all/utils/fixture.rs:335:12 | 23 | impl Fixture { | ------------ methods in this implementation ... 335 | pub fn install_local_geckodriver(&self) -> PathBuf { | ^^^^^^^^^^^^^^^^^^^^^^^^^ ... 350 | pub fn install_local_chromedriver(&self) -> PathBuf { | ^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: function `wbg_test_browser` is never used --> tests/all/utils/fixture.rs:566:8 | 566 | pub fn wbg_test_browser() -> Fixture { | ^^^^^^^^^^^^^^^^ warning: `wasm-pack` (test "all") generated 3 warnings (run `cargo fix --test "all" -p wasm-pack` to apply 1 suggestion) Finished `test` profile [unoptimized + debuginfo] target(s) in 25.54s Running unittests src/lib.rs (target/debug/deps/wasm_pack-cb4060096c413646) running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Running unittests src/main.rs (target/debug/deps/wasm_pack-26dec3df5cc6d125) running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Running tests/all/main.rs (target/debug/deps/all-5ecb30ba88c8fb12) running 81 tests test manifest::it_doesnt_recurse_up_the_path_to_find_cargo_toml_when_default ... ok test stamps::load_stamp_from_non_existent_file - should panic ... ok test stamps::load_stamp ... ok test stamps::update_stamp ... ok test build::build_in_non_crate_directory_doesnt_panic ... ok test webdriver::can_install_geckodriver ... ok test generate::new_with_no_name_errors ... ok test generate::new_with_name_succeeds ... ok test download::all_latest_tool_download_urls_valid ... ok test manifest::it_creates_a_pkg_json_with_correct_files_on_node ... ok test manifest::it_gets_the_default_name_prefix ... ok test manifest::it_gets_the_name_prefix_passed_from_cli ... ok test manifest::it_recurses_up_the_path_to_find_cargo_toml ... ok test manifest::it_errors_when_wasm_bindgen_is_not_declared ... ok test manifest::it_gets_the_crate_name_provided_path ... ok test readme::it_copies_a_readme_provided_path ... ok test manifest::it_gets_the_crate_name_default_path ... ok test manifest::it_creates_a_package_json_default_path ... ok test manifest::it_creates_a_pkg_json_with_correct_files_on_nomodules ... ok test manifest::it_creates_a_package_json_provided_path_with_scope ... ok test manifest::configure_wasm_bindgen_debug_incorrectly_is_error ... ok test manifest::it_lists_license_files_in_files_field_of_package_json ... ok test readme::it_copies_a_readme_default_path ... ok test license::it_copies_all_licenses_provided_path ... ok test license::it_copies_a_license_default_path ... ok test license::it_copies_a_license_provided_path ... ok test license::it_copies_a_non_standard_license_provided_path ... ok test license::it_copies_all_licenses_default_path ... ok test manifest::it_checks_has_cdylib_wrong_crate_type ... ok test manifest::it_creates_a_package_json_provided_path ... ok test manifest::it_creates_a_package_json_with_npm_dependencies_provided_by_wasm_bindgen ... ok test manifest::it_creates_a_pkg_json_in_out_dir ... ok test manifest::it_creates_a_package_json_with_correct_files_when_out_name_is_provided ... ok test manifest::it_creates_a_package_json_with_correct_keys_when_types_are_skipped ... ok test wasm_opt::misconfigured ... ok test manifest::it_sets_keywords_field_if_available_in_cargo_toml ... ok test manifest::it_sets_homepage_field_if_available_in_cargo_toml ... ok test manifest::it_recognizes_a_map_during_depcheck ... ok test lockfile::it_gets_wasm_bindgen_version_from_dependencies ... ok test log_level::log_level_warn ... FAILED test log_level::log_level_error ... FAILED test log_level::log_level_info ... FAILED test build::it_should_build_js_hello_world_example ... FAILED test log_level::quiet ... FAILED test build::it_should_build_js_hello_world_example_with_custom_target_dir ... FAILED test build::build_custom_profile ... FAILED test lockfile::it_gets_wasm_bindgen_version_in_crate_inside_workspace ... ok test build::dash_dash_web_target_has_error_on_old_bindgen ... ok test readme::it_ignores_a_disabled_readme ... FAILED test build::it_should_not_make_a_pkg_json_if_passed_no_pack ... FAILED test manifest::it_checks_has_cdylib_default_path ... ok test manifest::it_checks_has_cdylib_provided_path ... ok test manifest::it_does_not_error_when_wasm_bindgen_is_declared ... ok test lockfile::it_gets_wasm_bindgen_test_version ... ok test lockfile::it_gets_wasm_bindgen_version ... ok test build::build_with_and_without_wasm_bindgen_debug ... FAILED test wasm_opt::off_in_dev ... ok test wasm_opt::enable_in_dev ... ok test build::build_different_profiles ... FAILED test build::renamed_crate_name_works ... FAILED test manifest::parse_crate_data_returns_unused_keys_in_cargo_toml ... FAILED test wasm_opt::disable_in_release ... ok test wasm_opt::on_in_release ... ok test build::build_from_new ... FAILED test build::build_with_arbitrary_cargo_options ... FAILED test build::it_should_build_crates_in_a_workspace ... FAILED test build::build_crates_with_same_names ... FAILED test build::build_force ... FAILED test wasm_opt::custom_args ... ok test build::it_should_build_nested_project_with_transitive_dependencies ... FAILED test build::build_no_install ... FAILED test test::cdylib_not_required has been running for over 60 seconds test test::complains_about_missing_wasm_bindgen_test_dependency has been running for over 60 seconds test test::extra_options_is_passed_to_cargo_when_building_tests has been running for over 60 seconds test test::it_can_run_failing_tests has been running for over 60 seconds test test::it_can_run_node_tests has been running for over 60 seconds test test::it_can_run_tests_with_different_wbg_test_and_wbg_versions has been running for over 60 seconds test test::it_requires_node_or_a_browser has been running for over 60 seconds test test::renamed_crate_name_works has been running for over 60 seconds test test::test_output_is_printed_once_in_both_stdout_and_failures has been running for over 60 seconds test test::the_headless_flag_requires_a_browser has been running for over 60 seconds test test::extra_options_is_passed_to_cargo_when_building_tests ... ok test test::it_can_run_failing_tests ... ok test test::complains_about_missing_wasm_bindgen_test_dependency ... ok test test::renamed_crate_name_works ... ok test test::it_can_run_node_tests ... FAILED test test::it_can_run_tests_with_different_wbg_test_and_wbg_versions ... ok test test::cdylib_not_required ... ok test test::test_output_is_printed_once_in_both_stdout_and_failures ... FAILED test test::the_headless_flag_requires_a_browser ... ok test test::it_requires_node_or_a_browser ... ok failures: ---- log_level::log_level_warn stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpyboYQV/wasm-pack thread 'log_level::log_level_warn' (26357) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 16.01s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpyboYQV/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpyboYQV/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "--log-level" "warn" "build"` code=1 stdout="" stderr=``` warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 16.01s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpyboYQV/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- log_level::log_level_error stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack thread 'log_level::log_level_error' (26353) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack) Finished `release` profile [optimized] target(s) in 15.99s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "--log-level" "error" "build"` code=1 stdout="" stderr=``` warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack) Finished `release` profile [optimized] target(s) in 15.99s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpIIeJ06/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- log_level::log_level_info stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpSlVeQ9/wasm-pack thread 'log_level::log_level_info' (26354) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 15.95s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpSlVeQ9/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpSlVeQ9/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "--log-level" "info" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 15.95s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpSlVeQ9/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::it_should_build_js_hello_world_example stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp7ry14n/wasm-pack thread 'build::it_should_build_js_hello_world_example' (26336) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 15.64s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp7ry14n/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp7ry14n/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 15.64s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp7ry14n/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- log_level::quiet stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpEYrPZ0/wasm-pack thread 'log_level::quiet' (26358) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpEYrPZ0/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpEYrPZ0/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "--quiet" "build"` code=1 stdout="" stderr=``` error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpEYrPZ0/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::it_should_build_js_hello_world_example_with_custom_target_dir stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack thread 'build::it_should_build_js_hello_world_example_with_custom_target_dir' (26337) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack) Finished `release` profile [optimized] target(s) in 15.61s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack/target2/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--target-dir" "target2" "--all-features" "--offline"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack) Finished `release` profile [optimized] target(s) in 15.61s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack/target2/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpMhXWKd/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_custom_profile stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack thread 'build::build_custom_profile' (26326) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling cfg-if v1.0.4 Compiling once_cell v1.21.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack) Finished `my-custom-profile` profile [optimized] target(s) in 14.21s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/my-custom-profile/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--profile" "my-custom-profile"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Compiling wasm-bindgen-shared v0.2.114 Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling rustversion v1.0.22 Compiling bumpalo v3.20.2 Compiling cfg-if v1.0.4 Compiling once_cell v1.21.4 Compiling wasm-bindgen v0.2.114 Compiling syn v2.0.117 Compiling wasm-bindgen-macro-support v0.2.114 Compiling wasm-bindgen-macro v0.2.114 Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack) Finished `my-custom-profile` profile [optimized] target(s) in 14.21s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/my-custom-profile/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpO9wBEF/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- readme::it_ignores_a_disabled_readme stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpawfJC3/wasm-pack thread 'readme::it_ignores_a_disabled_readme' (26398) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 22.93s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpawfJC3/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpawfJC3/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 22.93s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpawfJC3/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::it_should_not_make_a_pkg_json_if_passed_no_pack stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmplvUQ7I/wasm-pack thread 'build::it_should_not_make_a_pkg_json_if_passed_no_pack' (26339) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 22.73s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmplvUQ7I/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmplvUQ7I/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--no-pack"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 22.73s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmplvUQ7I/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_with_and_without_wasm_bindgen_debug stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack [INFO]: found wasm-opt at "/usr/bin/wasm-opt" thread 'build::build_with_and_without_wasm_bindgen_debug' (26332) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling unicode-ident v1.0.24 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling whatever v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 25.14s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/whatever.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" \"--debug\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--dev"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling unicode-ident v1.0.24 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling whatever v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 25.14s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/whatever.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpQ5paEB/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" \"--debug\" ``` ---- build::build_different_profiles stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack thread 'build::build_different_profiles' (26327) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 27.63s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" \"--debug\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--dev"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling js-hello-world v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 27.63s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmppwfrBn/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" \"--debug\" ``` ---- build::renamed_crate_name_works stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack thread 'build::renamed_crate_name_works' (26340) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling wasm-bindgen-macro-support v0.2.120 Compiling wasm-bindgen-macro v0.2.120 Compiling foo v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack) Finished `release` profile [optimized] target(s) in 28.18s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/bar.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling wasm-bindgen-macro-support v0.2.120 Compiling wasm-bindgen-macro v0.2.120 Compiling foo v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack) Finished `release` profile [optimized] target(s) in 28.18s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/bar.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpGtXkdc/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- manifest::parse_crate_data_returns_unused_keys_in_cargo_toml stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack thread 'manifest::parse_crate_data_returns_unused_keys_in_cargo_toml' (26395) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [WARN]: :-) \"package.metadata.wasm-pack.profile.production\" is an unknown key and will be ignored. Please check your Cargo.toml. [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling whatever v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack) Finished `release` profile [optimized] target(s) in 28.52s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/whatever.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [WARN]: :-) \"package.metadata.wasm-pack.profile.production\" is an unknown key and will be ignored. Please check your Cargo.toml. [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling whatever v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack) Finished `release` profile [optimized] target(s) in 28.52s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/whatever.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpnJuHNq/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_from_new stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack thread 'build::build_from_new' (26329) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling unicode-ident v1.0.24 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling console_error_panic_hook v0.1.7 Compiling generated-project v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack/generated-project) warning: function `set_panic_hook` is never used --> src/utils.rs:1:8 | 1 | pub fn set_panic_hook() { | ^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default Finished `release` profile [optimized] target(s) in 32.04s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/generated_project.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack/generated-project/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack/generated-project"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling unicode-ident v1.0.24 Compiling once_cell v1.21.4 Compiling cfg-if v1.0.4 Compiling wasm-bindgen-shared v0.2.120 Compiling wasm-bindgen v0.2.120 Compiling console_error_panic_hook v0.1.7 Compiling generated-project v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack/generated-project) warning: function `set_panic_hook` is never used --> src/utils.rs:1:8 | 1 | pub fn set_panic_hook() { | ^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default Finished `release` profile [optimized] target(s) in 32.04s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/generated_project.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmp4VhpCZ/wasm-pack/generated-project/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_with_arbitrary_cargo_options stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpvedP55/wasm-pack thread 'build::build_with_arbitrary_cargo_options' (26333) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 31.53s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpvedP55/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpvedP55/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--no-default-features"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 31.53s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpvedP55/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::it_should_build_crates_in_a_workspace stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack thread 'build::it_should_build_crates_in_a_workspace' (26335) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah/Cargo.toml: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling blah v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah) Finished `release` profile [optimized] target(s) in 32.07s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/blah.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah/Cargo.toml: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling blah v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah) Finished `release` profile [optimized] target(s) in 32.07s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/blah.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpm6Ym9y/wasm-pack/blah/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_crates_with_same_names stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack thread 'build::build_crates_with_same_names' (26325) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling somename v0.1.1 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename2) Compiling somename v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename1) Finished `release` profile [optimized] target(s) in 32.47s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/somename.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename1/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename1" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling somename v0.1.1 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename2) Compiling somename v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename1) Finished `release` profile [optimized] target(s) in 32.47s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/somename.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpdqIKvh/wasm-pack/somename1/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_force stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpFKo7QE/wasm-pack thread 'build::build_force' (26328) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 32.80s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpFKo7QE/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpFKo7QE/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--mode" "force"` code=1 stdout="" stderr=``` [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 32.80s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpFKo7QE/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::it_should_build_nested_project_with_transitive_dependencies stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack thread 'build::it_should_build_nested_project_with_transitive_dependencies' (26338) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling project_b v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/project_b) Compiling project_a v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/project_a) Compiling main_project v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/main) Finished `release` profile [optimized] target(s) in 34.15s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/main_project.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/main/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/main" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Compiling project_b v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/project_b) Compiling project_a v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/project_a) Compiling main_project v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/main) Finished `release` profile [optimized] target(s) in 34.15s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.120 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.120 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/main_project.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpgo4sKU/wasm-pack/main/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- build::build_no_install stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpM1jmxV/wasm-pack thread 'build::build_no_install' (26331) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 34.09s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpM1jmxV/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpM1jmxV/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "build" "--mode" "no-install"` code=1 stdout="" stderr=``` [INFO]: Checking for the Wasm target... [INFO]: Compiling to Wasm... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Blocking waiting for file lock on artifact directory Finished `release` profile [optimized] target(s) in 34.09s error: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! Error: Running the wasm-bindgen CLI Caused by: Running the wasm-bindgen CLI Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1 full command: \"/usr/bin/wasm-bindgen\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/release/js_hello_world.wasm\" \"--out-dir\" \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpM1jmxV/wasm-pack/pkg\" \"--typescript\" \"--target\" \"bundler\" ``` ---- test::it_can_run_node_tests stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack thread 'test::it_can_run_node_tests' (26406) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected failure. code=1 stderr=`````` [INFO]: Checking for the Wasm target... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Compiling wbg-test-node v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.34s warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s Running unittests src/lib.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/wbg_test_node-3adc23dfa57a276b.wasm) Running tests/node.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-4e2fe6089e4159ab.wasm) Error: executing `wasm-bindgen` over the Wasm file Caused by: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! error: test failed, to rerun pass `--test node` Caused by: process didn\'t exit successfully: `/usr/bin/wasm-bindgen-test-runner /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-4e2fe6089e4159ab.wasm` (exit status: 1) note: test exited abnormally; to see the full output pass --no-capture to the harness. Error: Running Wasm tests with wasm-bindgen-test failed Caused by: Running Wasm tests with wasm-bindgen-test failed Caused by: failed to execute `cargo test`: exited with exit status: 1 full command: cd \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack\" && CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER=\"/usr/bin/wasm-bindgen-test-runner\" WASM_BINDGEN_TEST_ONLY_NODE=\"1\" \"cargo\" \"test\" \"--target\" \"wasm32-unknown-unknown\" ``` ``` command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "test" "--node"` code=1 stdout="no tests to run!\n" stderr=``` [INFO]: Checking for the Wasm target... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Compiling wbg-test-node v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.34s warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s Running unittests src/lib.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/wbg_test_node-3adc23dfa57a276b.wasm) Running tests/node.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-4e2fe6089e4159ab.wasm) Error: executing `wasm-bindgen` over the Wasm file Caused by: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! error: test failed, to rerun pass `--test node` Caused by: process didn\'t exit successfully: `/usr/bin/wasm-bindgen-test-runner /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-4e2fe6089e4159ab.wasm` (exit status: 1) note: test exited abnormally; to see the full output pass --no-capture to the harness. Error: Running Wasm tests with wasm-bindgen-test failed Caused by: Running Wasm tests with wasm-bindgen-test failed Caused by: failed to execute `cargo test`: exited with exit status: 1 full command: cd \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpRnmWkZ/wasm-pack\" && CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER=\"/usr/bin/wasm-bindgen-test-runner\" WASM_BINDGEN_TEST_ONLY_NODE=\"1\" \"cargo\" \"test\" \"--target\" \"wasm32-unknown-unknown\" ``` ---- test::test_output_is_printed_once_in_both_stdout_and_failures stdout ---- Created fixture at /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpoW7yJq/wasm-pack thread 'test::test_output_is_printed_once_in_both_stdout_and_failures' (26410) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library/core/src/ops/function.rs:250:5: Unexpected stdout, failed fn(var) └── var as str: no tests to run! command=`cd "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpoW7yJq/wasm-pack" && env -u CARGO_TERM_COLOR WASM_PACK_CACHE="/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/test_cache" "/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/debug/wasm-pack" "test" "--node"` code=1 stdout="no tests to run!\n" stderr=``` [INFO]: Checking for the Wasm target... warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Compiling test-output-printed-once v0.1.0 (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpoW7yJq/wasm-pack) Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.35s warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s Running unittests src/lib.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/test_output_printed_once-a90bb4db37119218.wasm) Running tests/node.rs (/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-688e25cd45ae8bb6.wasm) Error: executing `wasm-bindgen` over the Wasm file Caused by: it looks like the Rust project used to create this Wasm file was linked against version of wasm-bindgen that uses a different bindgen format than this binary: rust Wasm file schema version: 0.2.114 this binary schema version: 0.2.118 Currently the bindgen format is unstable enough that these two schema versions must exactly match. You can accomplish this by either updating this binary or the wasm-bindgen dependency in the Rust project. You should be able to update the wasm-bindgen dependency with: cargo update -p wasm-bindgen --precise 0.2.118 don\'t forget to recompile your Wasm file! Alternatively, you can update the binary with: cargo install -f wasm-bindgen-cli --version 0.2.114 if this warning fails to go away though and you\'re not sure what to do feel free to open an issue at https://github.com/wasm-bindgen/wasm-bindgen/issues! error: test failed, to rerun pass `--test node` Caused by: process didn\'t exit successfully: `/usr/bin/wasm-bindgen-test-runner /home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/wasm32-unknown-unknown/debug/deps/node-688e25cd45ae8bb6.wasm` (exit status: 1) note: test exited abnormally; to see the full output pass --no-capture to the harness. Error: Running Wasm tests with wasm-bindgen-test failed Caused by: Running Wasm tests with wasm-bindgen-test failed Caused by: failed to execute `cargo test`: exited with exit status: 1 full command: cd \"/home/buildozer/aports/community/wasm-pack/src/wasm-pack-0.14.0/target/t/.tmpoW7yJq/wasm-pack\" && CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER=\"/usr/bin/wasm-bindgen-test-runner\" WASM_BINDGEN_TEST_ONLY_NODE=\"1\" \"cargo\" \"test\" \"--target\" \"wasm32-unknown-unknown\" ``` failures: build::build_crates_with_same_names build::build_custom_profile 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::it_should_build_crates_in_a_workspace build::it_should_build_js_hello_world_example build::it_should_build_js_hello_world_example_with_custom_target_dir build::it_should_build_nested_project_with_transitive_dependencies build::it_should_not_make_a_pkg_json_if_passed_no_pack 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 readme::it_ignores_a_disabled_readme test::it_can_run_node_tests test::test_output_is_printed_once_in_both_stdout_and_failures test result: FAILED. 59 passed; 22 failed; 0 ignored; 0 measured; 0 filtered out; finished in 97.04s error: test failed, to rerun pass `--test all` >>> ERROR: wasm-pack: check failed >>> wasm-pack: Uninstalling dependencies... ( 1/50) Purging .makedepends-wasm-pack (20260506.073800) ( 2/50) Purging rustc-dev (1.95.0-r0) ( 3/50) Purging bzip2-dev (1.0.8-r6) ( 4/50) Purging cargo-auditable (0.7.4-r0) ( 5/50) Purging cmake (4.2.3-r0) ( 6/50) Purging curl-dev (8.20.0-r0) ( 7/50) Purging openssl-dev (3.5.6-r0) ( 8/50) Purging samurai (1.2-r8) ( 9/50) Purging wasi-sdk (27-r1) (10/50) Purging wasi-libcxx (22.1.3-r0) (11/50) Purging wasi-compiler-rt (22.1.3-r0) (12/50) Purging zstd-dev (1.5.7-r2) (13/50) Purging zstd (1.5.7-r2) (14/50) Purging binaryen (123-r1) (15/50) Purging cargo-generate (0.23.8-r0) (16/50) Purging wasm-bindgen (0.2.118-r0) (17/50) Purging cargo (1.95.0-r0) (18/50) Purging nodejs (24.14.1-r1) (19/50) Purging ca-certificates (20260413-r0) Executing ca-certificates-20260413-r0.post-deinstall (20/50) Purging rust-wasm (1.95.0-r0) (21/50) Purging rust (1.95.0-r0) (22/50) Purging wasi-libc (0.20250204-r1) (23/50) Purging ada-libs (3.3.0-r0) (24/50) Purging brotli-dev (1.2.0-r1) (25/50) Purging brotli (1.2.0-r1) (26/50) Purging c-ares-dev (1.34.6-r0) (27/50) Purging icu-libs (78.1-r0) (28/50) Purging libarchive (3.8.7-r0) (29/50) Purging libbz2 (1.0.8-r6) (30/50) Purging libgit2 (1.9.3-r0) (31/50) Purging libpsl-dev (0.21.5-r3) (32/50) Purging libpsl-utils (0.21.5-r3) (33/50) Purging libssh2 (1.11.1-r1) (34/50) Purging libuv (1.52.1-r0) (35/50) Purging lld22 (22.1.3-r0) (36/50) Purging lld22-libs (22.1.3-r0) (37/50) Purging llhttp (9.3.1-r0) (38/50) Purging llvm22-libs (22.1.3-r0) (39/50) Purging nghttp2-dev (1.69.0-r0) (40/50) Purging rhash-libs (1.4.6-r0) (41/50) Purging scudo-malloc (22.1.3-r0) (42/50) Purging simdjson (4.2.4-r0) (43/50) Purging simdutf (9.0.0-r0) (44/50) Purging sqlite-libs (3.53.0-r0) (45/50) Purging zlib-dev (1.3.2-r0) (46/50) Purging icu-data-en (78.1-r0) (47/50) Purging libffi (3.5.2-r1) (48/50) Purging libidn2-dev (2.3.8-r0) (49/50) Purging libxml2 (2.13.9-r1) (50/50) Purging xz-libs (5.8.3-r0) Executing busybox-1.37.0-r31.trigger OK: 431.5 MiB in 103 packages