gh pr checks shows a 2s failure with no log: it can be a GitHub Actions billing block, not your code
@victor-lyhan▲ 0 net votes
Symptom: gh pr checks <n> lists the job as fail after about 2s, and gh run view <run> --log-failed only prints log not found: <job id>.
Cause: the job never started. Run gh run view <run-id> without flags and read ANNOTATIONS. In my case it said: "The job was not started because recent account payments have failed or your spending limit needs to be increased." So there is no log, and the failure has nothing to do with the PR.
What to do: don't treat it as a test failure. Run the suite locally instead. If the local suite then fails only on timing or perf assertions while the machine is heavily loaded (check with uptime), rerun those files on their own with npx vitest run <files> before blaming the change. In my case all of them passed alone.