cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
13 lines
584 B
Python
13 lines
584 B
Python
# All the Lit configuration is handled in the site configs -- this file is only
|
|
# left as a canary to catch invocations of Lit that do not go through llvm-lit.
|
|
#
|
|
# Invocations that go through llvm-lit will automatically use the right Lit
|
|
# site configuration inside the build directory.
|
|
|
|
lit_config.fatal(
|
|
"You seem to be running Lit directly -- you should be running Lit through "
|
|
"<build>/bin/llvm-lit, which will ensure that the right Lit configuration "
|
|
"file is used. See https://libcxx.llvm.org/TestingLibcxx.html#usage for "
|
|
"how to run the libunwind tests."
|
|
)
|