Job build-deploy on ubuntu-latest Checking out concept-collection/turing-sphere at 3e80a0cf Container started from catthehacker/ubuntu:act-latest ▸ actions/checkout@v4 Using cofferdam's built-in checkout (actions/checkout@v4) concept-collection/turing-sphere is already checked out at 3e80a0cf (cofferdam checks out before the job starts) ▸ actions/setup-node@v4 Using cached actions/setup-node@v4 (49933ea5288c) Attempting to download 24... (node:55) [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.19.0 - x64 from https://nodejs.org/dist/v24.19.0/node-v24.19.0-linux-x64.tar.gz Extracting ... [command]/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /cofferdam/temp/100da5d7-9a50-4284-8cf6-460a90bf5ddd -f /cofferdam/temp/ffcdb513-951b-4208-9ff8-c94fb79d9a96 Adding to the cache ... Done ▾ Environment details node: v24.19.0 npm: 11.17.0 yarn: WARNING: Cache action is only supported on GHES version >= 3.5. If you are on version >=3.5 Please check with GHES admin if Actions cache service is enabled or not. ▸ Check out numbl (sibling dependency) Cloning into '/cofferdam/workspace/../../numbl'... ▸ Run npm ci --ignore-scripts npm warn deprecated mp4-muxer@5.2.2: This library is superseded by Mediabunny. Please migrate to it. added 125 packages, and audited 127 packages in 3s 18 packages are looking for funding run `npm fund` for details 6 vulnerabilities (1 moderate, 5 high) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. ▸ Run npm run test:node -- --skip-without-gpu > turing-sphere@0.1.0 test:node > vite-node scripts/test-node.ts --skip-without-gpu Warning: Couldn't load Vulkan: libvulkan.so.1: cannot open shared object file: No such file or directory at operator() (/home/runner/work/node-webgpu/node-webgpu/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:363) SKIP no WebGPU available here, so these checks did not run. No WebGPU adapter available Dawn reaches the GPU through Vulkan on Linux and Windows, Metal on macOS, so a headless box may have no adapter at all. DAWN_FLAGS='backend=vulkan' makes it explain itself. ▸ Run npm run build > turing-sphere@0.1.0 build > tsc --noEmit && vite build vite v5.4.21 building for production... transforming... ✓ 508 modules transformed. rendering chunks... computing gzip size... dist/test.html  0.39 kB │ gzip: 0.26 kB dist/index.html  11.93 kB │ gzip: 3.63 kB dist/assets/test-Az5FKarw.js  11.85 kB │ gzip: 5.30 kB dist/assets/main-BEHJneJI.js  567.21 kB │ gzip: 147.17 kB dist/assets/runSpec-CQAWpuTj.js 1,412.84 kB │ gzip: 398.06 kB  (!) Some chunks are larger than 500 kB after minification. Consider: - Using dynamic import() to code-split the application - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit. ✓ built in 5.01s ▸ actions/configure-pages@v5 Using cofferdam's built-in configure-pages (actions/configure-pages@v5) This site will be served at https://vault1.fly.dev/concept-collection/turing-sphere/site/ ▸ actions/upload-pages-artifact@v3 Using cached actions/upload-pages-artifact@v3 (56afc609e742) ▸ Archive artifact ▾ Archive artifact ./ ./test.html ./assets/ ./assets/main-BEHJneJI.js ./assets/runSpec-CQAWpuTj.js ./assets/test-Az5FKarw.js ./index.html ▸ Upload artifact Using cofferdam's built-in upload-artifact (actions/upload-artifact@v4) Uploading artifact github-pages (1 file, 2027520 bytes) ▸ actions/deploy-pages@v4 Using cofferdam's built-in deploy-pages (actions/deploy-pages@v4) Deployed 5 files to https://vault1.fly.dev/concept-collection/turing-sphere/site/ ▸ Post actions/setup-node@v4 (node:668) [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