From 4caa34249b7a398277e1d11bc4df4c1985180883 Mon Sep 17 00:00:00 2001 From: Tristan Simas Date: Wed, 18 Nov 2026 16:16:31 -0500 Subject: [PATCH] shipped_run: look for the deliberate crash's trace under the kept state #2136 moved this lookup to qt_drive's OUTDIR with the other two; but the crash check runs the app directly (shipped_fault), which writes its trace under kept/state. The APK build then failed every time with 'a faulted run exited -11 with 0 trace file(s)'. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01RnH6dT7wdh7i4tjJZQdFu3 --- tools/android/shipped_run.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tools/android/shipped_run.py b/tools/android/shipped_run.py index 3b2b852c6..6d2831577 100644 --- a/tools/android/shipped_run.py +++ b/tools/android/shipped_run.py @@ -219,7 +219,9 @@ def main(runtime: Path, app: Path, site_packages: Path) -> int: f"{len(errors)} error file(s)); TOAD_SHIPPED_KEEP=1 keeps its scratch folder", file=sys.stderr) return 1 print("shipped app ran every view kind and bound key on a scratch bus") - fault = fault_trace_failure(out / "state", shipped, recipes) + # The deliberate crash runs the app directly (shipped_fault), not through qt_drive, so its + # trace is under the kept state, not qt_drive's OUTDIR. + fault = fault_trace_failure(work / "kept" / "state", shipped, recipes) if fault: print(f"error: the shipped app's fault trace: {fault}", file=sys.stderr) return 1