20.1.0 only published headers

[nschonni]

Looks like the build finished https://unofficial-builds.nodejs.org/logs/202305031550-v20.1.0/ but only the headers were promoted to https://unofficial-builds.nodejs.org/download/release/v20.1.0/

[rvagg]

No space left on device

root@infra-digitalocean-ubuntu1804-x64-2:/home/nodejs# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.9G     0  7.9G   0% /dev
tmpfs           1.6G  688K  1.6G   1% /run
/dev/vda1        97G   96G  1.2G  99% /
tmpfs           7.9G     0  7.9G   0% /dev/shm
tmpfs           5.0M   24K  5.0M   1% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/vda15      105M  7.6M   97M   8% /boot/efi
/dev/sda        992G   54G  889G   6% /home/nodejs/download/release
tmpfs           1.6G     0  1.6G   0% /run/user/0

root@infra-digitalocean-ubuntu1804-x64-2:/home/nodejs# du -sh *
8.0K    bin
71G     download
28G     download-release-local-55
1.6G    logs
6.2G    staging
2.0M    unofficial-builds
16K     var

I don't know what download-release-local-55 is, May 9th 2022 apparently:

drwxr-xr-x   4 nodejs root    4096 May  9  2022 download
drwxr-xr-x 138 nodejs nodejs  4096 May  9  2022 download-release-local-55

but that's all sitting on the root disk and filling it up. I'm guessing someone was doing some kind of upgrade or manual release and copied existing files. So I'm making a call that we don't need this and that I'll remove it, rebuild the current recipie containers cause it looks like they're not properly cooked, and then try and rerun the build.

[richardlau]

I don't know what download-release-local-55 is, May 9th 2022 apparently:

drwxr-xr-x   4 nodejs root    4096 May  9  2022 download
drwxr-xr-x 138 nodejs nodejs  4096 May  9  2022 download-release-local-55

but that's all sitting on the root disk and filling it up. I'm guessing someone was doing some kind of upgrade or manual release and copied existing files. So I'm making a call that we don't need this and that I'll remove it, rebuild the current recipie containers cause it looks like they're not properly cooked, and then try and rerun the build.

It's the downloads from before we attached a larger disk to the server, although the comment would suggest it should be a different disk: #55 (comment)

[richardlau]

ah the one in #55 (comment) didn't have local in it's name 🤷

[rvagg]

cleaned it out, cleaned out docker to rebuild everything from scratch, rebooted and ... it's not coming back online

[rvagg]

hard power-cycle in digital ocean console fixed it .. working on rebuilding the containers and setting it up again

[rvagg]

@sxa I've had to remove the riscv64 recipe manually on the server to get past this:

 => ERROR [4/5] RUN curl https://ci.adoptopenjdk.net/userContent/riscv/riscv_toolchain_linux64.tar.xz | tar xJf - -C /opt                                    0.5s
------
 > [4/5] RUN curl https://ci.adoptopenjdk.net/userContent/riscv/riscv_toolchain_linux64.tar.xz | tar xJf - -C /opt:
#0 0.361   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#0 0.361                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
#0 0.389 xz: (stdin): File format not recognized
#0 0.390 tar: Child returned status 1
#0 0.390 tar: Error is not recoverable: exiting now
------
Dockerfile:24
--------------------
  22 |              xz-utils
  23 |
  24 | >>> RUN curl https://ci.adoptopenjdk.net/userContent/riscv/riscv_toolchain_linux64.tar.xz | tar xJf - -C /opt
  25 |
  26 |     COPY --chown=node:node run.sh /home/node/run.sh
--------------------
ERROR: failed to solve: process "/bin/sh -c curl https://ci.adoptopenjdk.net/userContent/riscv/riscv_toolchain_linux64.tar.xz | tar xJf - -C /opt" did not complet
e successfully: exit code: 2

can you handle this? on the next merge in this repo it's going to pull again and fail to build properly because of this. Otherwise we'll need to remove it from here.

[rvagg]

They're building now, just taking a long time, but at least some of the assets should show up once they're done; I see armv6l and x64-musl ready to go, x64-glibc-217 is currently in progress. See https://unofficial-builds.nodejs.org/logs/202305041049-v20.1.0/

[rvagg]

https://unofficial-builds.nodejs.org/download/release/v20.1.0/ minus riscv