"build from tarball" github action is flaky?

[sam-github]

It was introduced in #32129

It failed in the completely unrelated #32828 (which introduced only one change, marking another test as flaky).

Its not clear why, I didn't find a way to see any relevant logs when looking at its failure in https://github.com/nodejs/node/pull/32828/checks?check_run_id=583849189

• Version:
• Platform:
• Subsystem:

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

[sam-github]

#32825 (comment) failed as well

[richardlau]

I've no idea if it's related but there was a reported degradation for GitHub Actions today: https://www.githubstatus.com/incidents/2k3z9fkr9z5g

[jkleinsc]

FWIW... I think it was related to the GitHub Actions issue. If you look at this build: https://github.com/nodejs/node/runs/584292438, the "Make tarball" step took around 37 minutes, but in both of the failures list above that step ran around an hour or so before failing.

[sam-github]

OK, lets close, we can reopen if its recurring.

[Trott]

This is failing in my fork. Is there a way to have it only run in the nodejs/node repo and not in forks? And if so, is that something I control on my fork, or something we would put into the action workflow itself?

[targos]

@Trott You can disable actions in your fork here: https://github.com/Trott/io.js/settings/actions