Skip to content

Actions: MiSTerOrganize/MiSTer_OpenBOR_7533

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
771 workflow runs
771 workflow runs

Filter by Workflow

⌥ + click/return to exclude

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
DB dispatch: manual Dispatch DB rebuild #20: Manually run by MiSTerOrganize
10s main
main
10s
CI: cdn_ready.sh - do not name one caller's action in the shared succ… Build MiSTer ARM #570: Commit e5ae42e pushed by MiSTerOrganize
26m 28s main
main
26m 28s
openbor-diff-harness Diff Harness #101: Commit e5ae42e pushed by MiSTerOrganize
1m 42s main
main
1m 42s
CI: gate both DB-rebuild dispatch paths on CDN propagation Build MiSTer ARM #569: Commit 7cf6edf pushed by MiSTerOrganize
28m 27s main
main
28m 27s
openbor-diff-harness Diff Harness #100: Commit 7cf6edf pushed by MiSTerOrganize
1m 9s main
main
1m 9s
openbor-diff-harness Diff Harness #99: Commit aa3ec99 pushed by MiSTerOrganize
1m 26s main
main
1m 26s
CI: run-name -- let a push fall back to GitHub's own default Build MiSTer ARM #568: Commit aa3ec99 pushed by MiSTerOrganize
1m 27s main
main
1m 27s
harness: fix the clone line I broke adding the timeout The timeout commit left the clone as: timeout 600 git clone --filter=blob:none \n https://... where that is a LITERAL backslash-n, not a line continuation. git took it as its first argument, rejected it, and printed its usage text -- which reads like a network problem in the log but is a malformed command. The backslash was eaten crossing bash heredoc -> Python string -> file. That is the trap already written down in this project: script... Build MiSTer ARM #567: Commit 038bc72 pushed by MiSTerOrganize
28m 42s main
main
28m 42s
openbor-diff-harness Diff Harness #98: Commit 038bc72 pushed by MiSTerOrganize
1m 27s main
main
1m 27s
harness: bound the headless build so a stalled fetch fails fast Run 32274919740 sat 2h45m in "Build OpenBOR headless (x86-64)", a step that normally takes about a minute, and would have run to GitHub's 6-hour default before failing with nothing useful in the log. Not a code fault. All seven gates ahead of it passed, the same script succeeded twice the day before, and that commit only touched apply_patches.py, which runs after the clone. It stalled in the network fetch: the clone uses --filter=blob:none... Build MiSTer ARM #566: Commit 4b9b486 pushed by MiSTerOrganize
28m 39s main
main
28m 39s
openbor-diff-harness Diff Harness #97: Commit 4b9b486 pushed by MiSTerOrganize
2m 32s main
main
2m 32s
openbor-diff-harness Diff Harness #96: Commit 0a5e34b pushed by MiSTerOrganize
2h 47m 5s main
main
2h 47m 5s
TEMPORARY DIAG: trace the flame death sequence Three fixes changed nothing and every static check passes -- right entity, nomove 1 confirmed setting PAIN_CONFIG_FALL_DISABLE, both patches verified present in the emitted source at the correct lines. So the wrong thing is the model of the runtime, not the reading of the file. Seven probes in death_try_sequence_damage, gated on models named "flame": entry state/flags/animating, both fall-first early returns, both set_death sites, and both REMOVE_VANISH bl... Build MiSTer ARM #565: Commit 0a5e34b pushed by MiSTerOrganize
28m 14s main
main
28m 14s
openbor-diff-harness Diff Harness #95: Commit 3dce0b8 pushed by MiSTerOrganize
1m 17s fix-death-falldisable
fix-death-falldisable
1m 17s
death: removal half (flame freeze) Build MiSTer ARM #564: Manually run by MiSTerOrganize
27m 43s fix-death-falldisable
fix-death-falldisable
27m 43s
openbor-diff-harness Diff Harness #94: Commit d16a430 pushed by MiSTerOrganize
2m 29s fix-death-falldisable
fix-death-falldisable
2m 29s
death: skip fall phase when fall disabled (TMNT-RP flame) Build MiSTer ARM #563: Manually run by MiSTerOrganize
28m 44s fix-death-falldisable
fix-death-falldisable
28m 44s
refresh latest (workflow_dispatch) Refresh latest release #56: Manually run by MiSTerOrganize
11s main
main
11s
Merge: Lust Rush pause-menu fixes, loading read-out, engine v2 Hardware-confirmed by the user: Lust Rush's pause menu now works, and ATOV and TMNT-RP did not regress -- the two carts whose update scripts do not run during pause, so the guarded branch was already false for them. * modal-menu guard: a cart's update script no longer runs inside our pause menu. Lust Rush ships its own pause menu, hides the native one at pauseoffset 999,999 and drives it by injecting FLAG_ESC; alwaysupdate is ... Build MiSTer ARM #562: Commit 8599d13 pushed by MiSTerOrganize
19m 6s main
main
19m 6s
openbor-diff-harness Diff Harness #93: Commit 8599d13 pushed by MiSTerOrganize
5m 8s main
main
5m 8s
openbor-diff-harness Diff Harness #92: Commit b5688e1 pushed by MiSTerOrganize
1m 39s pausemenu-diag3
pausemenu-diag3
1m 39s
ENGINE_VER 2 + synth derives version Build MiSTer ARM #561: Manually run by MiSTerOrganize
28m 15s pausemenu-diag3
pausemenu-diag3
28m 15s
openbor-diff-harness Diff Harness #91: Commit 6fbafaa pushed by MiSTerOrganize
26s pausemenu-diag3
pausemenu-diag3
26s
MREC_ENGINE_VER 2 + modal-menu guard Build MiSTer ARM #560: Manually run by MiSTerOrganize
20s pausemenu-diag3
pausemenu-diag3
20s
openbor-diff-harness Diff Harness #90: Commit d480300 pushed by MiSTerOrganize
1m 55s pausemenu-diag3
pausemenu-diag3
1m 55s