You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the promotion script as the dist user appears to back up that theory -- v18.0.0-test202202249be1dcff34 was the identifier for the test builds I ran:
I suspect I've run into nodejs/build#2020 where the destination dist directory intentionally had its permissions changed and I was running builds with the same identifier over more than a five day period. I don't need the v18.0.0-test202202249be1dcff34 build, so I'll remove the unpromoted assets from staging.
Activity
targos commentedon Apr 20, 2022
I don't know why there's nothing in the
v8-canaryfolder. Release builds are green. For example yesterday:https://ci-release.nodejs.org/job/iojs+release/8404/
@nodejs/build-infra
targos commentedon Apr 20, 2022
The files are copied to
custom. That's probably the cause of the problem.richardlau commentedon Apr 20, 2022
Unlikely, that has always been the case -- the builds are staged in
customand the promotion script is supposed to be copying the files tov8-canarybased on the directory name: https://github.com/nodejs/build/blob/5e2ae08283c75eff51de04635883446dce23ad8b/ansible/www-standalone/tools/promote/settings#L16-L18Given the timings, I think what may have happened is that the test build I was running while adding new release machines for Node.js 18 has caused an issue while promoting
testbuilds and making the promotion script bail before promotingv8-canary(the order isnightly,next-nightly,rc,test,v8-canary:https://github.com/nodejs/build/blob/371bb7626abe773a56c7c62e76d0a551ba1b9717/ansible/www-standalone/tools/promote/promote_nightly.sh#L14-L43). I'll try to figure out what that is and how to recover.
richardlau commentedon Apr 20, 2022
Running the promotion script as the
distuser appears to back up that theory --v18.0.0-test202202249be1dcff34was the identifier for the test builds I ran:I suspect I've run into nodejs/build#2020 where the destination dist directory intentionally had its permissions changed and I was running builds with the same identifier over more than a five day period. I don't need the
v18.0.0-test202202249be1dcff34build, so I'll remove the unpromoted assets from staging.richardlau commentedon Apr 20, 2022
Looks promising:
richardlau commentedon Apr 20, 2022
The missing canary builds are all now available.
vsemozhetbyt commentedon Apr 20, 2022
Thank you!