Job build-deploy on ubuntu-latest Checking out proof-of-concept/cymsimweb at cffea67f Container started from catthehacker/ubuntu:act-latest ▸ actions/checkout@v4 Using mochi's built-in checkout (actions/checkout@v4) proof-of-concept/cymsimweb is already checked out at cffea67f (mochi checks out before the job starts) ▸ actions/setup-node@v4 Using cached actions/setup-node@v4 (49933ea5288c) Attempting to download 24... (node:21) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) Bad credentials Falling back to download directly from Node Acquiring 24.21.0 - x64 from https://nodejs.org/dist/v24.21.0/node-v24.21.0-linux-x64.tar.gz Extracting ... [command]/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /mochi/temp/29c2dea5-34b0-43b1-8ef0-3e1fad45c6e6 -f /mochi/temp/558a200f-783b-4069-b399-69f979279f01 Adding to the cache ... Done ▾ Environment details node: v24.21.0 npm: 11.19.0 yarn: ▸ Run npm ci added 36 packages, and audited 37 packages in 3s 6 packages are looking for funding run `npm fund` for details found 0 vulnerabilities npm warn install-scripts 2 packages have install scripts not yet covered by allowScripts: npm warn install-scripts esbuild@0.25.12 (postinstall: node install.js) npm warn install-scripts webgpu@0.4.0 (postinstall: node build/postinstall.js) npm warn install-scripts npm warn install-scripts Run `npm install-scripts ls` to review, or `npm install-scripts approve ` to allow. ▸ Run npm run test:cpu > cymsimweb@0.1.0 test:cpu > node --test tests/*.test.ts ✔ FFT of a sine peaks at the right bin (9.341526ms) ✔ incremental STFT tracks a chirp's centroid (26.330769ms) ✔ WAV encoding and playback scaling (0.7402ms) ✔ presets parse without issues (12.519889ms) ✔ round trip through YAML preserves the configuration (6.197824ms) ✔ Python fixture config normalizes to itself (0.28091ms) ✔ partial documents take defaults (0.431431ms) ✔ unknown keys, wrong types and bad values are reported (1.29998ms) ✔ CPU time loop reproduces the Python run (dent-free, float64) (1871.047334ms) ✔ linear run matches Python tightly (no chaotic amplification) (1795.853812ms) ✔ DKT stiffness matches the Python (autodiff) element (3.616252ms) ✔ DKT rigid modes, constant curvature and twist (2.034541ms) ✔ Jacobi eigenvalues and plane fit (0.522501ms) ✔ disk mesh is a valid manifold with good quality (30.141461ms) ✔ mesh matches the Python mesher exactly (3.105492ms) ✔ locate returns barycentric weights that sum to one (0.85806ms) ✔ dent-free shell matches the Python assembly (2.345262ms) ✔ element and rigid-mode checks (32.198863ms) ✔ contact patch matches Python (6.464124ms) ℹ tests 19 ℹ suites 0 ℹ pass 19 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 4994.786723 ▸ Run npm run build > cymsimweb@0.1.0 build > tsc --noEmit && vite build vite v6.4.3 building for production... transforming... ✓ 40 modules transformed. rendering chunks... computing gzip size... dist/index.html  3.61 kB │ gzip: 1.14 kB dist/assets/index-2hg7xKhU.css  4.17 kB │ gzip: 1.38 kB dist/assets/index-DtM_1NK4.js 421.37 kB │ gzip: 140.79 kB ✓ built in 2.23s ▸ actions/configure-pages@v5 Using mochi's built-in configure-pages (actions/configure-pages@v5) This site will be served at https://cymsimweb--proof-of-concept.vault1-sites.magland.org/ ▸ actions/upload-pages-artifact@v3 Using cached actions/upload-pages-artifact@v3 (56afc609e742) ▸ Archive artifact ▾ Archive artifact ./ ./index.html ./assets/ ./assets/index-2hg7xKhU.css ./assets/index-DtM_1NK4.js ▸ Upload artifact Using mochi's built-in upload-artifact (actions/upload-artifact@v4) Uploading artifact github-pages (1 file, 441856 bytes) ▸ actions/deploy-pages@v4 Using mochi's built-in deploy-pages (actions/deploy-pages@v4) Deployed 3 files to https://cymsimweb--proof-of-concept.vault1-sites.magland.org/ ▸ Post actions/setup-node@v4 (node:210) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) Cleaning up the job container