vasilito
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).
56 lines
2.2 KiB
INI
56 lines
2.2 KiB
INI
import lit
|
|
|
|
# Use lit's internal shell to help guarantee test portability.
|
|
config.test_format = lit.formats.ShTest(execute_external=False)
|
|
|
|
# %ProtectFileCheckOutput should precede a FileCheck call if and only if the
|
|
# call's textual output affects test results. It's usually easy to tell: just
|
|
# look for redirection or piping of the FileCheck call's stdout or stderr.
|
|
#
|
|
# Examples:
|
|
#
|
|
# ; Test another program, using FileCheck to verify its textual output.
|
|
# ; Only FileCheck's exit status affects test results, so a bare FileCheck
|
|
# ; call is sufficient and more convenient for debugging.
|
|
# ;
|
|
# ; RUN: %t | FileCheck %s
|
|
# ; CHECK: {{[0-9]+\.0}}
|
|
#
|
|
# ; Test FileCheck itself, but only examine its exit status, so a bare
|
|
# ; FileCheck call is still sufficient and more convenient for debugging.
|
|
# ;
|
|
# ; RUN: FileCheck -input-file %s %s
|
|
# ; CHECK: {{[0-9]+\.0}}
|
|
# ; 5.0
|
|
#
|
|
# ; Check that the FileCheck trace is off by default. The first FileCheck
|
|
# ; call's textual output affects test results, so it requires
|
|
# ; %ProtectFileCheckOutput to be safe.
|
|
# ;
|
|
# ; RUN: %ProtectFileCheckOutput FileCheck -input-file %s %s 2>&1 \
|
|
# ; RUN: | FileCheck -allow-empty -check-prefix QUIET %s
|
|
# ;
|
|
# ; CHECK: {{[0-9]+\.0}}
|
|
# ; 5.0
|
|
# ; QUIET-NOT: expected string found in input
|
|
#
|
|
# ; Check that the FileCheck trace is on when FILECHECK_OPTS=-v.
|
|
# ; FILECHECK_OPTS must be set after %ProtectFileCheckOutput, which clears
|
|
# ; FILECHECK_OPTS beforehand.
|
|
# ;
|
|
# ; RUN: %ProtectFileCheckOutput FILECHECK_OPTS=-v \
|
|
# ; RUN: FileCheck -dump-input=never -input-file %s %s 2>&1 \
|
|
# ; RUN: | FileCheck -check-prefix TRACE %s
|
|
# ;
|
|
# ; CHECK: {{[0-9]+\.0}}
|
|
# ; 5.0
|
|
# ; TRACE: expected string found in input
|
|
#
|
|
# %ProtectFileCheckOutput's purpose is to ensure correct test results when
|
|
# developers set FileCheck environment variables (e.g.,
|
|
# FILECHECK_OPTS=-dump-input=fail) to tweak the output of FileCheck while
|
|
# debugging tests. If a developer sets values that affect FileCheck's exit
|
|
# status (e.g., FILECHECK_OPTS=-strict-whitespace), he shouldn't be surprised
|
|
# that test results throughout all test suites are affected.
|
|
config.substitutions.append(("%ProtectFileCheckOutput", "env -u FILECHECK_OPTS"))
|