You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fp-stability: auto-install Verrou on first use (download prebuilt), hard-fail if it can't
Running ./mfc.sh fp-stability with no Verrou present now installs it via the bootstrap (downloads the pinned prebuilt from verrou-dist; source build as fallback) and proceeds, instead of SKIP+exit-0; a failed install is now a hard error. _find_verrou no longer accepts a bare system valgrind on PATH (it has no 'verrou' tool and would only fail at run time) — that case reads as 'Verrou absent' so it gets installed. CI drops the separate Install/Verify Verrou steps; the run does it. Tests added for the discovery logic.
raiseMFCException("Verrou install failed (see output above). Fix the issue and re-run, install manually with `bash toolchain/bootstrap/verrou.sh`, or pass --verrou-binary PATH.")
670
+
verrou_bin=_find_verrou()
671
+
ifnotverrou_binornotos.path.isfile(verrou_bin):
672
+
raiseMFCException("Verrou install reported success but no valgrind binary was found under $VERROU_HOME.")
673
+
returnverrou_bin
674
+
675
+
661
676
deffp_stability():
662
677
verrou_bin=ARG("verrou_binary") or_find_verrou()
663
678
ifnotverrou_binornotos.path.isfile(verrou_bin):
664
-
cons.print("[bold yellow]SKIP[/bold yellow]: Verrou not found (it is a compiled Valgrind tool, not a pip package).")
665
-
cons.print(" Install it (Linux; ~20 min source build) with: [bold]bash toolchain/bootstrap/verrou.sh[/bold]")
666
-
cons.print(" Or point at an existing build with --verrou-binary PATH or $VERROU_HOME.")
667
-
sys.exit(0)
679
+
ifARG("verrou_binary"):
680
+
raiseMFCException(f"--verrou-binary {ARG('verrou_binary')!r} not found or not executable.")
0 commit comments