This topic was moved here from #compiler development > ci by Anton.
I renamed this to prevent a naming collision with the zulip export.
It's nice to have all the github CI machines easily available in the weekend :)
The zig-benchmarks CI step server is temporarily offline for updates.
Back up
We have a minici error on the main branch, I'm on it
expected type 'canonical_names.ModuleIdentityId', found 'canonical_names.ModuleNameId
I'm working on a fix for flaky issue:
| === CLI Test Runner ===
| 632 tests, 3 workers, 240s timeout, backends: interpreter, dev
|
| Glue generator: /Users/runner/work/roc/roc/zig-out/bin/roc, glue-opt=default, full-targets=false
|
| timed out roc test round-trips JSON parse and encode (239121.7ms, phase=run)
| child command timed out; preserved work dir: /Users/runner/work/roc/roc/.zig-cache/roc-test/work/5-4ac202caf347fc1e-5
| signal 9
| stderr: stuck: child command timed out after 238999ms:
Anton said:
I'm working on a fix for flaky issue:
| === CLI Test Runner === | 632 tests, 3 workers, 240s timeout, backends: interpreter, dev | | Glue generator: /Users/runner/work/roc/roc/zig-out/bin/roc, glue-opt=default, full-targets=false | | timed out roc test round-trips JSON parse and encode (239121.7ms, phase=run) | child command timed out; preserved work dir: /Users/runner/work/roc/roc/.zig-cache/roc-test/work/5-4ac202caf347fc1e-5 | signal 9 | stderr: stuck: child command timed out after 238999ms:
Thank you (again!) for looking into this!
I think it's fixed now, let me know if you still see it (with commit 876f7c2 already on your branch)
I'd like to give zlint (like clippy but for zig) a try. Mainly for new contributors it's nice to have a quick check of zig best practices. What do you think?
sure! I assume in addition to the current tidy.zig?
Yes, in addition
Sorry to bother, but I had a question about the test_runner artifact. In d50491d77b84dec1d21d7da71d8e7bae70462b91, it looks like all meaningful references were removed to the test_runner artifact. In particular, after that commit, test_runner_exe is never referenced by a b.addRunArtifact call. I am just curious whether I am missing something silly (I am trying to work my way through the build/test system) or whether a failure to remove the code that adds the test_runner (and the main in src/cli/test/test_runner.zig) was a simple oversight.
If the latter, I'd be glad to build a PR for removing that dead code, if that is okay! Please forgive me if this question is silly/stupid -- as I said, I am attempting to grok the build/test system!
Will Hawkins said:
Sorry to bother, but I had a question about the
test_runnerartifact. In d50491d77b84dec1d21d7da71d8e7bae70462b91, it looks like all meaningful references were removed to thetest_runnerartifact. In particular, after that commit,test_runner_exeis never referenced by ab.addRunArtifactcall. I am just curious whether I am missing something silly (I am trying to work my way through the build/test system) or whether a failure to remove the code that adds thetest_runner(and themaininsrc/cli/test/test_runner.zig) was a simple oversight.If the latter, I'd be glad to build a PR for removing that dead code, if that is okay! Please forgive me if this question is silly/stupid -- as I said, I am attempting to grok the build/test system!
Also, I apologize if this channel was not the appropriate one for this question.
Maybe in the process of merging different PR's that wasn't removed (or somehow was added back).
I'm guessing an oversight... the parallel cli runner is an upgrade if I recall correctly
Luke Boswell said:
Maybe in the process of merging different PR's that wasn't removed (or somehow was added back).
Sounds good! Thank you for the confirmation! I will submit a PR with that code removed, if that sounds okay?
Will Hawkins said:
Luke Boswell said:
Maybe in the process of merging different PR's that wasn't removed (or somehow was added back).
Sounds good! Thank you for the confirmation! I will submit a PR with that code removed, if that sounds okay?
Thank you for triggering the CI on the PR -- it looks like there is a failure in CI on Windows. I will investigate ASAP!
That failure looks like it's happening on all the PRs
Windows is timing out for some reason.
If you are able to find the root cause that'd be great
Last updated: Jul 23 2026 at 13:15 UTC