Uninformative/cryptic error for `windows-latest` jobs

[abravalheri]

Description

On https://github.com/pypa/setuptools/actions/runs/21362919094/job/61506256194?pr=5163 I can see the following "error screen":

(I have already tried re-running the job).

After downloading and unzipping the logs, I can see:

2026-01-26T18:02:51.9860000Z Evaluating test.if
2026-01-26T18:02:51.9860000Z Evaluating: success()
2026-01-26T18:02:51.9860000Z Result: true
2026-01-26T18:02:51.9890000Z Requested labels: windows-latest
2026-01-26T18:02:51.9890000Z Job defined at: pypa/setuptools/.github/workflows/main.yml@refs/pull/5163/merge
2026-01-26T18:02:51.9890000Z Waiting for a runner to pick up this job...
2026-01-26T18:02:52.2640000Z Job is about to start running on the hosted runner: GitHub Actions 1000276405
2026-01-26T18:02:52.2640000Z Job is waiting for a hosted runner to come online.

Which is still not informative...

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• Ubuntu Slim
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• macOS 26 Arm64
• Windows Server 2022
• Windows Server 2025

Image version and build link

The question suggests that I should look For GitHub Actions, under "Set up job" -> "Runner Image" -> "Version". But I cannot find any button with Set up job written in it.

This is the link for the CI https://github.com/pypa/setuptools/actions/runs/21362919094/job/61506256194?pr=5163

Is it regression?

Yes. I believe so. The job runs without a problem in https://github.com/pypa/setuptools/actions/runs/21340582121/job/61419317940, the workflow file did not change.

Expected behavior

In both webGUI and logs I should be able to see relevant information for why the job is failing.

Actual behavior

The job fails without providing any relevant information to help the user understand why it fails.

Repro steps

Re-run the job in https://github.com/pypa/setuptools/actions/runs/21362919094/job/61506256194?pr=5163

[erik-bershel]

Hey @abravalheri! 👋

The issue is directly related to the change that resulted in this issue: #13590. It has already been rolled back. I'll leave this ticket on the board for now to raise awareness.

[abravalheri]

Hi @erik-bershel , thank you very much for the feedback.

Does it mean that worker-related errors will now have better logs/reporting?

[erik-bershel]

Does it mean that worker-related errors will now have better logs/reporting?

No, it was a one-time glitch. An unexpected result. We're investigating the cause and will try to avoid this in the future.

[dagood]

The issue is directly related to the change that resulted in this issue: #13590. It has already been rolled back. I'll leave this ticket on the board for now to raise awareness.

Did you mean to link a PR? That link points to this very issue thread.