failure
Deploy site
queued 1s ran 5s total 6s
1 jobs
1 failed
6s duration
— tests
0 artifacts
Step failed A step exited non-zero. Open the log for the failing command's output.
HTTPError: Request failed with status code 401 (Unauthorized): GET https://storage.bunnycdn.com/2044090/ HTTPError: Request failed with status code 401 (Unauthorized): GET https://storage.bunnycdn.com/2044090/
deploy
failuredeploy
Annotations
- ERROR HTTPError: Request failed with status code 401 (Unauthorized): GET https://storage.bunnycdn.com/2044090/
successSet up job
cloning hlassiege/panoplie @ d9bf20e0dfbd5ebf0934252927fb334877ed58a4action actions/setup-node@v4: node20 (_actions/actions/setup-node/v4)action R-J-dev/bunny-deploy@v2.1.1: node20 (_actions/R-J-dev/bunny-deploy/v2.1.1)
successCheckout code <1s
(checkout already performed by the runner — delivered as the read-only work disk)
successSetup Node.js 4s
ciguest: network up (172.30.0.2/30 via 172.30.0.1)ciguest: starting dockerd (overlay2, data-root on scratch)ciguest: dockerd is readyciguest: loaded baked image postgres_16-alpine.tar.gz: Loaded image: postgres:16-alpineciguest: 1 baked image archive(s) loaded (no per-job registry pull needed)ciguest: logged into registry registry.rickub.com as rickubisExplicit: explicit? falseevaluating 0 versionsmatch not foundAttempting to download 22...No manifest cachedGetting manifest from actions/node-versions@main(node:549) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.(Use `node --trace-deprecation ...` to show where the warning was created)check 26.13.0 satisfies 22check 26.12.1 satisfies 22check 26.12.0 satisfies 22check 26.11.1 satisfies 22check 26.11.0 satisfies 22check 26.10.0 satisfies 22check 26.9.0 satisfies 22check 26.8.2 satisfies 22check 26.8.1 satisfies 22check 26.8.0 satisfies 22check 26.7.0 satisfies 22check 26.6.0 satisfies 22check 26.5.1 satisfies 22check 26.5.0 satisfies 22check 26.4.0 satisfies 22check 26.3.1 satisfies 22check 26.3.0 satisfies 22check 26.2.0 satisfies 22check 26.1.0 satisfies 22check 26.0.0 satisfies 22check 24.22.2 satisfies 22check 24.22.1 satisfies 22check 24.22.0 satisfies 22check 24.21.0 satisfies 22check 24.20.0 satisfies 22check 24.19.0 satisfies 22check 24.18.1 satisfies 22check 24.18.0 satisfies 22check 24.17.0 satisfies 22check 24.16.0 satisfies 22check 24.15.0 satisfies 22check 24.14.1 satisfies 22check 24.14.0 satisfies 22check 24.13.1 satisfies 22check 24.13.0 satisfies 22check 24.12.0 satisfies 22check 24.11.1 satisfies 22check 24.11.0 satisfies 22check 24.10.0 satisfies 22check 24.9.0 satisfies 22check 24.8.0 satisfies 22check 24.7.0 satisfies 22check 24.6.0 satisfies 22check 24.5.0 satisfies 22check 24.4.1 satisfies 22check 24.4.0 satisfies 22check 24.3.0 satisfies 22check 24.2.0 satisfies 22check 24.1.0 satisfies 22check 24.0.2 satisfies 22check 24.0.1 satisfies 22check 24.0.0 satisfies 22check 22.23.4 satisfies 22arm64===x64 && darwin===linuxx64===x64 && darwin===linuxarm64===x64 && linux===linuxx64===x64 && linux===linuxmatched 22.23.4Acquiring 22.23.4 - x64 from https://github.com/actions/node-versions/releases/download/22.23.4-39619033003/node-22.23.4-linux-x64.tar.gzDownloading https://github.com/actions/node-versions/releases/download/22.23.4-39619033003/node-22.23.4-linux-x64.tar.gzDestination /tmp/7d64cf35-2cd3-4612-81b8-e87bd6aa99f1download completeExtracting ...Checking tar --versiontar (GNU tar) 1.34Copyright (C) 2021 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.Written by John Gilmore and Jay Fenlason.[command]/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /tmp/b8018a24-3596-4e97-afe6-6c98a9d0ea7e -f /tmp/7d64cf35-2cd3-4612-81b8-e87bd6aa99f1Adding to the cache ...Caching tool node 22.23.4 x64source dir: /tmp/b8018a24-3596-4e97-afe6-6c98a9d0ea7edestination /tmp/hostedtoolcache/node/22.23.4/x64finished caching tool
Environment details
node: v22.23.4npm: 10.9.9yarn:
##[add-matcher]/workspace/_actions/actions/setup-node/v4/.github/tsc.json##[add-matcher]/workspace/_actions/actions/setup-node/v4/.github/eslint-stylish.json##[add-matcher]/workspace/_actions/actions/setup-node/v4/.github/eslint-compact.json
successBuild site <1s
Run
node site/build.mjs
Site built in /workspace/panoplie/site/dist
failureDeploy to Bunny CDN ! <1s
Retrieving feature flagsRetrieving feature flagsRetrieving edgeStorageConfig
Retrieving file info
Retrieving file info for: 2044090/HTTPError: Request failed with status code 401 (Unauthorized): GET https://storage.bunnycdn.com/2044090/
Post Setup Node.js !
Caching for '' is not supported(node:601) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.(Use `node --trace-deprecation ...` to show where the warning was created)step failed: exit code 1 — Deploy to Bunny CDN
Annotations
HTTPError: Request failed with status code 401 (Unauthorized): GET https://storage.bunnycdn.com/2044090/
No test reports for this run.
Tell a job where its test runner writes its report and this tab fills in: how many tests passed, failed and were skipped, a bar of the result at a glance, then every failure first — with the assertion that failed and the output around it — over a per-suite list of cases and their durations. No scrolling a log for the word FAIL.
It is one reports: key on the job — a job key, not a step, so the report is collected whatever the job concluded. JUnit XML and go test -json are both understood, and most runners already emit one of them. reports: is a rickub extension and works only in .rickub/workflows/; in .github/workflows/ it is a parse error on purpose, because those files are also meant to run on github.com.