arm64v8 builds not updating

Question

arm64v8 builds not updating

staticfloat opened this issue 3 years ago · comments

The 1.6.0-beta1 and 1.6.0-rc1 builds do not appear to have an arm64v8 build available, while the 1.5.X builds do.

Tianon Gravi · Answer 1 · Wed Feb 10 2021 04:15:07 GMT+0800 (China Standard Time)

It seems our build server is having trouble downloading the artifacts? 😕

+ curl -fL -o julia.tar.gz.asc https://julialang-s3.julialang.org/bin/linux/aarch64/1.6/julia-1.6.0-rc1-linux-aarch64.tar.gz.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to ewr1-cache.e.ip.saba.us port 443: Connection refused

(Although if I hit that URL locally, it downloads just fine. 😕)

Tianon Gravi · Answer 2 · Wed Feb 10 2021 04:16:04 GMT+0800 (China Standard Time)

I got slightly more data doing it interactively:

root@90f22ee01963:/# curl -fL -D- -o julia.tar.gz.asc https://julialang-s3.julialang.org/bin/linux/aarch64/1.6/julia-1.6.0-rc1-linux-aarch64.tar.gz.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0HTTP/2 302 
server: Varnish
retry-after: 0
location: https://ewr1-cache.e.ip.saba.us/julialang2/bin/linux/aarch64/1.6/julia-1.6.0-rc1-linux-aarch64.tar.gz.asc
accept-ranges: bytes
date: Tue, 09 Feb 2021 20:15:41 GMT
via: 1.1 varnish
x-served-by: cache-lga21958-LGA
x-cache: HIT
x-cache-hits: 0
x-timer: S1612901741.008251,VS0,VE1
content-length: 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to ewr1-cache.e.ip.saba.us port 443: Connection refused

Elliot Saba · Answer 3 · Wed Feb 10 2021 04:58:02 GMT+0800 (China Standard Time)

Ah, seems we had some caching trouble. Can you try again now please?

Tianon Gravi · Answer 4 · Wed Feb 10 2021 05:08:10 GMT+0800 (China Standard Time)

My own build on a different (testing) daemon on that same server was successful!

For the official build, this should get picked up by https://doi-janky.infosiftr.net/job/multiarch/job/arm64v8/job/julia/218/console (which should happen as soon as https://doi-janky.infosiftr.net/job/multiarch/job/arm64v8/job/gcc/226/console finishes, hopefully within the next hour or so).

Elliot Saba · Answer 5 · Wed Feb 10 2021 05:09:05 GMT+0800 (China Standard Time)

You're a legend. Thanks @tianon!

Tianon Gravi · Answer 6 · Wed Feb 10 2021 05:11:16 GMT+0800 (China Standard Time)

Just for posterity, arm32v7 was affected by this also (it's built on the same server), and so when it finally gets some queue time it should hopefully be fixed too. 👍

(docker-library/official-images#9590 updated debian which always does a number on our queues, so it's gonna take some time to work back through 😅)

Mosè Giordano · Answer 7 · Wed Feb 10 2021 05:15:25 GMT+0800 (China Standard Time)

Unfortunately there is no build for armv7l 😞

Tianon Gravi · Answer 8 · Wed Feb 10 2021 05:18:10 GMT+0800 (China Standard Time)

Oh! I guess that's just for 1.0, sorry (but same underlying build failure). 😬