-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New build failures - validation fail on "version" #38
Comments
My best guess is that this is linked to reports of the website returning 500 errors -- @ljharb reported them again yesterday (in Slack) and Line 13 in ca6a7c5
Line 35 in ca6a7c5
|
richardlau
added a commit
that referenced
this issue
May 6, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
richardlau
added a commit
that referenced
this issue
May 7, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
richardlau
added a commit
that referenced
this issue
May 7, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
richardlau
added a commit
that referenced
this issue
May 7, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
richardlau
added a commit
that referenced
this issue
May 7, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
richardlau
added a commit
that referenced
this issue
May 7, 2022
Trap empty `NODE_VERSION`, e.g. if fetching `index.tab` fails. Refs: #38
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Got a slew of failures in my inbox today that I don't have time to fully investigate right now. I've looked at a couple of the failure logs, one for 17 and one for 18, and I think they're likely all the same, here's one for 18:
https://launchpadlibrarian.net/599646903/buildlog_snap_ubuntu_focal_armhf_node18_BUILDING.txt.gz
Current config looks good: https://github.com/nodejs/snap/blob/node18/snapcraft.yaml
But the previous update doesn't! d3a364b, it's missing the
version
. That's weird, and a problem.Need to investigate:
version
from somewhere and letting that get through, it should error out or ideally not even pick up a bad version in the first place!The text was updated successfully, but these errors were encountered: