Stream: wasmtime

Topic: ✔ CI / merge queue flaky?


view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 19:53):

Has anyone been having trouble with the merge queue?

This PR keeps bouncing from the merge queue "due to failed status checks" but then when I dig into the details of the action (for example) then there is no actually test job that is failing or anything like that, it is just the "Record the result of testing and building steps" job that is failing and cancelling all the other jobs that haven't completed yet. But my understanding is that job is the job that is just joining all the other jobs we fanned out, and isn't actually doing anything itself? So I am not sure why it is even doing anything before all the tests have finished?

Anyone else seen this? Know what's going on?

Returns a summary of the resources required to instantiate this module or component. Potential uses of the returned information: Determining whether your pooling allocator configuration supports ...
A fast and secure runtime for WebAssembly. Contribute to bytecodealliance/wasmtime development by creating an account on GitHub.

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 19:55):

looks like the part of the "Record the result of testing and building steps" that is failing is the case where some job we were waiting on joining got cancelled

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 19:55):

so I guess I'm just getting really unlucky and github keeps cancelling runners for some of these jobs?

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 19:58):

oh interesting, it looks like there was an actual error (well -Werror equivalent) but the github actions seems to think it was a cancellation rather than a failure?

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 19:58):

https://github.com/bytecodealliance/wasmtime/actions/runs/5731092473/job/15531259573#step:5:161

A fast and secure runtime for WebAssembly. Contribute to bytecodealliance/wasmtime development by creating an account on GitHub.

view this post on Zulip Notification Bot (Aug 01 2023 at 20:03):

fitzgen (he/him) has marked this topic as resolved.

view this post on Zulip Peter Huene (Aug 01 2023 at 20:04):

Yeah, I think it was just cancelled right when the Linux job succeeded to mark it ready for adding it to the queue

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 20:04):

I don't know, it happened multiple times, seems weird if it was a timing thing

view this post on Zulip Peter Huene (Aug 01 2023 at 20:09):

oh sorry, was looking at the wrong thing (github is also very slow for me at the moment)

view this post on Zulip fitzgen (he/him) (Aug 01 2023 at 20:09):

no worries! at least I figured out what was going on

view this post on Zulip Peter Huene (Aug 01 2023 at 20:09):

:+1:

view this post on Zulip Alex Crichton (Aug 02 2023 at 06:40):

@fitzgen (he/him) check the windows builers when that happens -- https://github.com/bytecodealliance/wasmtime/actions/runs/5731092473/job/15531259573

A fast and secure runtime for WebAssembly. Contribute to bytecodealliance/wasmtime development by creating an account on GitHub.

view this post on Zulip Alex Crichton (Aug 02 2023 at 06:40):

oh I think you found it

view this post on Zulip Alex Crichton (Aug 02 2023 at 06:40):

but the windows builders are known where if they cancel the rest of the run then they're I guess slow enough that they themselves appear cancelled after the failure (I don't know why this doesn't happen on Linux/macOS)


Last updated: Dec 23 2024 at 13:07 UTC