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).
22 lines
890 B
Plaintext
22 lines
890 B
Plaintext
# REQUIRES: x86
|
|
|
|
# FIXME(gkm): This test is fast on a Release tree, and slow (~10s) on
|
|
# a Debug tree mostly because of llvm-mc. Is there a way to prefer the
|
|
# fast installed llvm-mc rather than the slow one in our Debug tree?
|
|
|
|
# If headers and offsets are proper, then ...
|
|
#
|
|
# 1) llvm-objdump will not crash, and exit with good status
|
|
#
|
|
# 2) Summary encodings from the input object will match
|
|
# those from the linked output
|
|
#
|
|
# 3) Encodings & symbols from the input object will match
|
|
# those from the linked output
|
|
|
|
# RUN: %python %S/tools/generate-cfi-funcs.py --seed=johnnyapple >%t.s
|
|
# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin19.0.0 -emit-compact-unwind-non-canonical=true -o %t.o %t.s
|
|
# RUN: %lld -Z -L%S/Inputs/MacOSX.sdk/usr/lib -lSystem -o %t %t.o
|
|
# RUN: llvm-objdump --unwind-info --syms %t %t.o >%t.dump
|
|
# RUN: %python %S/tools/validate-unwind-info.py %t.dump
|