CI not running on PR? · cranelift

Any GitHub-CI wizards present who would be able to debug why https://github.com/bytecodealliance/wasmtime/pull/1570 has no CI tests (none pending/queued/...)? The PR doesn't change any config/metadata files, and tests are clean locally.

Fix long-range (non-colocated) aarch64 calls to not use Arm64Call reloc, and fix simplejit to use new long-distance call. by cfallin · Pull Request #1570 · bytecodealliance/wasmtime

Previously, every call was lowered on AArch64 to a call instruction, which takes a signed 26-bit PC-relative offset. Including the 2-bit left shift, this gives a range of +/- 128 MB. Longer-distanc...

Chris Fallin (May 05 2020 at 00:51):

The last rebase/force-push of mine didn't seem to kick the test-runner in the right way either

Alex Crichton (May 05 2020 at 02:34):

@Chris Fallin I clicked on the actions tab of the repo and it says GitHub is having issues

Alex Crichton (May 05 2020 at 02:34):

Typically a force.push should.retrigger but now they may just have issues

Chris Fallin (May 05 2020 at 02:35):

OK, thanks, will wait till their infra is back up before poking it further :-)

Alex Crichton (May 05 2020 at 02:35):

https://www.githubstatus.com/incidents/ljygds069np9

Incident on 2020-05-05 00:45 UTC

GitHub's Status Page - Incident on 2020-05-05 00:45 UTC.

Chris Fallin (May 05 2020 at 16:37):

Something kind of odd is happening here again. I force-pushed and the resulting runs ended with a 404 in a "download artifacts" step; forced a re-run and now the git checkout is failing with:

git checkout --progress --force 692f9e4ff3379b6f1bf6dbd01fd9d7ca1ba8b921
##[error]fatal: reference is not a tree: 692f9e4ff3379b6f1bf6dbd01fd9d7ca1ba8b921
##[error]Git checkout failed with exit code: 128
##[error]Exit code 1 returned from process: file name '/home/runner/runners/2.169.1/bin/Runner.PluginHost', arguments 'action "GitHub.Runner.Plugins.Repository.v1_0.CheckoutTask, Runner.Plugins"'.

(link: https://github.com/bytecodealliance/wasmtime/pull/1570/checks?check_run_id=646758917)

Disk space error? Or something else? Not sure how to debug...

Fix long-range (non-colocated) aarch64 calls to not use Arm64Call reloc, and fix simplejit to use new long-distance call. by cfallin · Pull Request #1570 · bytecodealliance/wasmtime

Alex Crichton (May 05 2020 at 16:50):

uh...

Alex Crichton (May 05 2020 at 16:50):

that can happen if you restart a PR build b/c it's a bug in github actions

Alex Crichton (May 05 2020 at 16:50):

but this was just from a straight push?

Chris Fallin (May 05 2020 at 16:54):

That error came after I hit 'rerun jobs'; but the builds from the push also errored out, with a 404 while downloading aarch64 artifacts (I didn't save the logs, sorry; should have)