Alex Crichton (Sep 18 2025 at 14:43): Alex Crichton (Sep 18 2025 at 14:43):IBM got back to us to get native s390x runners for the Wasmtime repo. Looks like to take advantage of that a GitHub admin for the BA org will need to install an app. It also looks like part of that is also registering an "IBMid" with the same email address as whomever installs the app. Could I solicit a GitHub admin's assistance for this? Not urgent of course!
Till Schneidereit (Sep 18 2025 at 19:41):Working on installing it. Does it need access to repos other than Wasmtime?
Alex Crichton (Sep 18 2025 at 19:42):Just wasmtime
Till Schneidereit (Sep 18 2025 at 19:42):kk
Chris Fallin (Sep 18 2025 at 20:21):One thing I noticed reading the details here is that actions will only work for branches on the BA/wasmtime repo, not forks; this means that if we have an s390x runner in CI, we'll need to require that PRs come only from branches pushed to the main repo (at least if those jobs run). I don't know if that makes this entirely a nonstarter, or just pushes it to main-branch-only jobs, but it's something to note as it diverges from our current PR workflow
Alex Crichton (Sep 18 2025 at 20:23):Hm yeah I wasn't aware of that... It's not entirely a non-starter since most s390x CI goes through the merge queue which should count as "from the repo", so the only thing we need to worry about is the PR CI. By default that doesn't run s390x but we might be able to rig up "run on github with qemu if PR and run on native if merge queue"
Till Schneidereit (Sep 18 2025 at 20:40):that'd make sense to me, yes. In any case, the app is now installed and the repo approved on their end, so in theory things should be working
Alex Crichton (Sep 18 2025 at 20:41):gonna test things out in https://github.com/bytecodealliance/wasmtime/pull/11711
Alex Crichton (Sep 18 2025 at 20:43):ok well, PRs to the repo can use s390x, which is good, so no concerns there
Alex Crichton (Sep 18 2025 at 22:36):summary here in case folks are interested
Last updated: Dec 06 2025 at 06:05 UTC