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).
38 lines
1.9 KiB
Plaintext
38 lines
1.9 KiB
Plaintext
; Test incorrect syntax for -D# option is correctly diagnosed.
|
|
|
|
; Invalid variable name: starts with a digit.
|
|
RUN: %ProtectFileCheckOutput \
|
|
RUN: not FileCheck -D#10VALUE=10 --input-file %s %s 2>&1 \
|
|
RUN: | FileCheck %s --strict-whitespace --match-full-lines --check-prefix NUMERRCLINAME
|
|
|
|
NUMERRCLINAME:Global defines:1:46: error: invalid variable name
|
|
NUMERRCLINAME-NEXT:Global define #1: #10VALUE=10 (parsed as: {{\[\[#10VALUE:10\]\]}})
|
|
NUMERRCLINAME-NEXT: ^
|
|
|
|
; Invalid definition of pseudo variable.
|
|
RUN: %ProtectFileCheckOutput \
|
|
RUN: not FileCheck -D#@VALUE=10 --input-file %s %s 2>&1 \
|
|
RUN: | FileCheck %s --strict-whitespace --match-full-lines --check-prefix NUMERRCLIPSEUDO
|
|
|
|
NUMERRCLIPSEUDO:Global defines:1:45: error: definition of pseudo numeric variable unsupported
|
|
NUMERRCLIPSEUDO-NEXT:Global define #1: #@VALUE=10 (parsed as: {{\[\[#@VALUE:10\]\]}})
|
|
NUMERRCLIPSEUDO-NEXT: ^
|
|
|
|
; Invalid definition of an expression.
|
|
RUN: %ProtectFileCheckOutput \
|
|
RUN: not FileCheck -D#VALUE+2=10 --input-file %s %s 2>&1 \
|
|
RUN: | FileCheck %s --strict-whitespace --match-full-lines --check-prefix NUMERRCLITRAIL
|
|
|
|
NUMERRCLITRAIL:Global defines:1:51: error: unexpected characters after numeric variable name
|
|
NUMERRCLITRAIL-NEXT:Global define #1: #VALUE+2=10 (parsed as: {{\[\[#VALUE\+2:10\]\]}})
|
|
NUMERRCLITRAIL-NEXT: ^
|
|
|
|
; Invalid format for variable.
|
|
RUN: %ProtectFileCheckOutput \
|
|
RUN: not FileCheck -D#,VALUE=10 --input-file %s %s 2>&1 \
|
|
RUN: | FileCheck %s --strict-whitespace --match-full-lines --check-prefix NUMERRCLIFMT
|
|
|
|
NUMERRCLIFMT:Global defines:1:45: error: invalid matching format specification in expression
|
|
NUMERRCLIFMT-NEXT:Global define #1: #,VALUE=10 (parsed as: {{\[\[#,VALUE:10\]\]}})
|
|
NUMERRCLIFMT-NEXT: ^
|