Add a GitHub Actions workflow that runs the spec-runner under Pernosco #1346
Conversation
lopopolo
force-pushed
the
pernosco-integration
branch
2 times, most recently
from
1722f32
to
d5d1b14
Compare
lopopolo
force-pushed
the
pernosco-integration
branch
from
f745be2
to
47f9828
Compare
|
Gah! I don't want to merge trunk in. |
lopopolo
force-pushed
the
pernosco-integration
branch
from
b63f553
to
150447a
Compare
|
ok trying again with the latest trunk and reverting 13e4b32. |
lopopolo
force-pushed
the
pernosco-integration
branch
from
150447a
to
3918f45
Compare
|
Note: I've been pushing empty commits to trigger rebuilds with unique SHAs as the Pernosco folks iterate on the GitHub Actions integration. I'm engaging with them separately over email. |
|
Woohoo! The Pernosco integration works! Here's the debugger shell at the segfault: https://pernos.co/debug/ckckYeQYH_xxvmI4mrZ4dQ/index.html#f{m[O4E,AA_,t[BA,GfU_,f{e[O3o,NUnC_,s{aVbAwlZAA,bOw,uVDZ4,oVFmu___ |
|
workflows won't kick off with conflicts. rebase incoming. this should be the moment of truth. |
lopopolo
force-pushed
the
pernosco-integration
branch
from
0a9e472
to
6c31466
Compare
|
pushing a rebase without the cherry pick to make sure the bug still reproduces. |
|
great! the latest rebase segfaults in GHA: https://github.com/artichoke/artichoke/runs/3528550124?check_suite_focus=true Pushing up the fix with a cherry-pick to the vendored mruby sources. |
Now that the Pernosco integration is known to be working as tested in the PR #1346, merge the workflow so we can generate reproduction environments for future crashes. Pernosco is enabled via environment variable on the runs of the `spec-runner`. This commit cherry-picks and squashes a couple of commits from #1346: - e1eea71 - 91bc825 Closes #1346.
This PR branches from 4321b46 which was known to cause a core dump in #1327.
This PR includes an improved version of the
crash.yamlworkflow which splits apart the invocations of the spec runner to one per job step and enables recording execution with Pernosco.cc @rocallahan @khuey
Opening this PR will kick off a run of the crash workflow which I expect to produce a core dump. Once I confirm the Pernosco GitHub Actions integration is working correctly, I'll rebase to the latest trunk and merge this PR.