Alex Crichton (Oct 01 2025 at 14:40): Alex Crichton (Oct 01 2025 at 14:40):Let's hold off for now. 2 PRs just merged without actually passing full CI in the merge queue
Alex Crichton (Oct 01 2025 at 14:41):I have no idea what's going on but something seems very buggy on GitHub's side
Alex Crichton (Oct 01 2025 at 14:41):specifically these top two PRs -- https://github.com/bytecodealliance/wasmtime/commits/2a2e8f62b9f20606f89a2e6619d6ece22eb57001 -- did not complete full CI and failed due to what looks like infrastructure reasons
Alex Crichton (Oct 01 2025 at 14:42):yet they still went ahead and merged, meaning that our "join" node in CI incorrectly deduced that all previous jobs passed
Alex Crichton (Oct 01 2025 at 14:43):looks like this is https://www.githubstatus.com/incidents/071h21gptcp0 as all the failing jobs are macos
bjorn3 (Oct 01 2025 at 14:55):I suspect https://github.com/bytecodealliance/wasmtime/blob/2a2e8f62b9f20606f89a2e6619d6ece22eb57001/.github/workflows/main.yml#L1204 passes for the failing macOS jobs. I don't know about what the possible status strings are for jobs, but for workflow runs it is: completed, action_required, cancelled, failure, neutral, skipped, stale, success, timed_out, in_progress, queued, requested, waiting, pending
Alex Crichton (Oct 01 2025 at 14:56):oof ok yeah we need to fix that
Alex Crichton (Oct 01 2025 at 14:56):also wow that is a lot of statuses...
Alex Crichton (Oct 01 2025 at 15:20):https://github.com/bytecodealliance/wasmtime/pull/11774
Alex Crichton (Oct 01 2025 at 16:41):ok that PR "correctly bounced" which means let's hold off merging until the current gha situation is under control
Alex Crichton (Oct 01 2025 at 16:41):after that though we shouldn't have to worry about this again
Last updated: Dec 06 2025 at 06:05 UTC