Job build-deploy on ubuntu-latest
Checking out concept-collection/math-webgpu-sandbox at 20d26046
Container started from catthehacker/ubuntu:act-latest
▸ actions/checkout@v4
Using cofferdam's built-in checkout (actions/checkout@v4)
concept-collection/math-webgpu-sandbox is already checked out at 20d26046 (cofferdam checks out before the job starts)
▸ actions/setup-node@v4
Using cached actions/setup-node@v4 (49933ea5288c)
Attempting to download 24...
(node:56) [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/08815672-ab67-4903-a1c8-276b4fdccac3 -f /cofferdam/temp/fc01dcad-3e3c-4985-af57-1ff8bc372486
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

added 115 packages, and audited 117 packages in 2s

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

> math-webgpu-sandbox@0.1.0 test:node
> vite-node scripts/test-node.ts --skip-without-gpu

node-webgpu 0.4.0 (Google Dawn)
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)

no WebGPU adapter
  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

> math-webgpu-sandbox@0.1.0 build
> tsc --noEmit && vite build

vite v5.4.21 building for production...
transforming...
✓ 487 modules transformed.
rendering chunks...
computing gzip size...
dist/test.html                       0.40 kB │ gzip:   0.26 kB
dist/index.html                      7.91 kB │ gzip:   2.65 kB
dist/assets/test-DepD7nFd.js         4.84 kB │ gzip:   2.16 kB
dist/assets/main-B9ckBcuE.js         8.14 kB │ gzip:   3.66 kB
dist/assets/session-DCyunjYA.js  1,397.28 kB │ gzip: 393.12 kB
✓ built in 2.90s

(!) 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.
▸ 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/math-webgpu-sandbox/site/
▸ actions/upload-pages-artifact@v3
Using cached actions/upload-pages-artifact@v3 (56afc609e742)
▸ Archive artifact
▾ Archive artifact
./
./assets/
./assets/session-DCyunjYA.js
./assets/test-DepD7nFd.js
./assets/main-B9ckBcuE.js
./test.html
./index.html
▸ Upload artifact
Using cofferdam's built-in upload-artifact (actions/upload-artifact@v4)
Uploading artifact github-pages (1 file, 1443840 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/math-webgpu-sandbox/site/
▸ Post actions/setup-node@v4
(node:670) [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