v8-canary builds missing since May 17, linux/darwin builds missing since Febrary

[joyeecheung]

Last one is AIX-only https://nodejs.org/download/v8-canary/v27.0.0-v8-canary202605175b9294c0c1/

I don't have access to release CI, so can't see what's wrong.

Also there has not been any linux/darwin builds since Feburary. Last one is https://nodejs.org/download/v8-canary/v26.0.0-v8-canary20260223fd2a99f348/

cc @nodejs/build

[targos]

Currently the main issue is the Rust version requirement

[richardlau]

We should be getting Linux builds now (I updated Rust on the RHEL 8 release machines (all archs)).

I'm suspicious that 20260517 is the last available downloadable build as we have in staging, e.g

total 644852
drwxrwxr-x    3 staging staging      4096 May 21 16:42 .
drwxrwxr-x 1968 staging staging    131072 May 21 11:14 ..
drwxrwxr-x    3 staging staging      4096 May 21 16:15 docs
-rw-rw-r--    1 staging staging         0 May 21 16:15 docs.done
-rw-rw-r--    1 staging staging  84122889 May 21 11:47 node-v27.0.0-v8-canary20260521da8e25c394-aix-ppc64.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 11:42 node-v27.0.0-v8-canary20260521da8e25c394-aix-ppc64.tar.gz.done
-rw-rw-r--    1 staging staging  10088167 May 21 16:15 node-v27.0.0-v8-canary20260521da8e25c394-headers.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 16:16 node-v27.0.0-v8-canary20260521da8e25c394-headers.tar.gz.done
-rw-rw-r--    1 staging staging    596044 May 21 16:16 node-v27.0.0-v8-canary20260521da8e25c394-headers.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 16:16 node-v27.0.0-v8-canary20260521da8e25c394-headers.tar.xz.done
-rw-rw-r--    1 staging staging  59259661 May 21 14:46 node-v27.0.0-v8-canary20260521da8e25c394-linux-arm64.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 14:48 node-v27.0.0-v8-canary20260521da8e25c394-linux-arm64.tar.gz.done
-rw-rw-r--    1 staging staging  31185060 May 21 14:48 node-v27.0.0-v8-canary20260521da8e25c394-linux-arm64.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 14:48 node-v27.0.0-v8-canary20260521da8e25c394-linux-arm64.tar.xz.done
-rw-rw-r--    1 staging staging  62065750 May 21 11:50 node-v27.0.0-v8-canary20260521da8e25c394-linux-ppc64le.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 11:52 node-v27.0.0-v8-canary20260521da8e25c394-linux-ppc64le.tar.gz.done
-rw-rw-r--    1 staging staging  31804332 May 21 11:52 node-v27.0.0-v8-canary20260521da8e25c394-linux-ppc64le.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 11:53 node-v27.0.0-v8-canary20260521da8e25c394-linux-ppc64le.tar.xz.done
-rw-rw-r--    1 staging staging  61479246 May 21 11:12 node-v27.0.0-v8-canary20260521da8e25c394-linux-s390x.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 11:15 node-v27.0.0-v8-canary20260521da8e25c394-linux-s390x.tar.gz.done
-rw-rw-r--    1 staging staging  31380780 May 21 11:14 node-v27.0.0-v8-canary20260521da8e25c394-linux-s390x.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 11:15 node-v27.0.0-v8-canary20260521da8e25c394-linux-s390x.tar.xz.done
-rw-rw-r--    1 staging staging  59602003 May 21 16:39 node-v27.0.0-v8-canary20260521da8e25c394-linux-x64.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 16:42 node-v27.0.0-v8-canary20260521da8e25c394-linux-x64.tar.gz.done
-rw-rw-r--    1 staging staging  32253548 May 21 16:42 node-v27.0.0-v8-canary20260521da8e25c394-linux-x64.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 16:42 node-v27.0.0-v8-canary20260521da8e25c394-linux-x64.tar.xz.done
-rw-rw-r--    1 staging staging 131238376 May 21 16:02 node-v27.0.0-v8-canary20260521da8e25c394.tar.gz
-rw-rw-r--    1 staging staging         0 May 21 16:11 node-v27.0.0-v8-canary20260521da8e25c394.tar.gz.done
-rw-rw-r--    1 staging staging  65089448 May 21 16:11 node-v27.0.0-v8-canary20260521da8e25c394.tar.xz
-rw-rw-r--    1 staging staging         0 May 21 16:12 node-v27.0.0-v8-canary20260521da8e25c394.tar.xz.done

which suggests something is going wrong with promotion for the canary builds.

[richardlau]

This is the cause:

dist@infra-digitalocean-ubuntu2204-x64-2:~$ /home/staging/tools/promote/promote_nightly.sh nodejs
Promoting v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3/node-v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3-win-x64.7z...
rm: cannot remove '/home/dist/nodejs/test/v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3/node-v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3-win-x64.7z': Permission denied
dist@infra-digitalocean-ubuntu2204-x64-2:~$

File cannot be removed because the target directory is old enough that it was made write only for the dist user:

total 93936
drwxr-xr-x   3 root root     4096 Apr 22 20:30 .
drwxr-xr-x 208 dist dist    20480 May  4 12:30 ..
-rw-r--r--   1 root root 24080359 Apr 22 20:00 node-v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3-win-x64.7z
-rw-r--r--   1 root root 38229424 Apr 22 20:00 node-v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3-win-x64.zip
-rw-r--r--   1 root root 33837056 Apr 22 20:00 node-v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3-x64.msi
-rw-r--r--   1 root root      742 Apr 22 20:30 SHASUMS256.txt
drwxr-xr-x   2 root root     4096 Apr 22 20:00 win-x64

I believe the culprit is https://ci-release.nodejs.org/job/iojs+release-mefi-pgo/4/ (cc @StefanStojanovic ) which hasn't set a datestring field so it ends up reusing the target directory and promotion breaks because it cannot overwrite the now restricted directory. To fix this I'm going to removed the staged directory for v26.0.0-test5becfbc91f904c6bf93ca0098ce34694a1bb4aa3 so that the promote script doesn't try to overwrite the existing files.

[richardlau]

https://nodejs.org/download/v8-canary/v27.0.0-v8-canary20260521da8e25c394/ now exists with AIX and Linux builds. As @targos mentioned, the other missing platforms will need a newer version of Rust.

[StefanStojanovic]

@richardlau yes, it is my fault, and I apologize. One question: in the datestring description, it says Only needed for nightly, and I was using test builds. For future builds of this job (I plan to run some today), what should I do to prevent the issue I caused? Just add datestring?

[StefanStojanovic]

I'll start another build soon. I'll put a datestring to avoid the issues described here.

[richardlau]

@richardlau yes, it is my fault, and I apologize. One question: in the datestring description, it says Only needed for nightly, and I was using test builds. For future builds of this job (I plan to run some today), what should I do to prevent the issue I caused? Just add datestring?

Yes, setting the datestring would be the simplest way.