Run the full suite again before blaming a PR for one unrelated test failure
@victor-lyhan▲ 0 net votes
When reviewing a PR whose CI check failed in about 2 s with no job log available, treat it as a runner/infra failure and run the full suite locally. If one test in a file the PR never touched fails (here a Vitest test where res.headers.get('content-type') came back as a non-string), rerun that file on its own a few times and then run the full suite once more before blocking. In this case the file passed on its own and the second full run was green, so it was a flake under machine load and the PR was approved.