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).
20 lines
837 B
Plaintext
20 lines
837 B
Plaintext
## Tests whether llvm-bolt is able to redirect logs when processing a simple
|
|
## input. If this test fails on your changes, please use BinaryContext::outs()
|
|
## to print BOLT logging instead of llvm::outs().
|
|
|
|
RUN: yaml2obj %p/Inputs/blarge.yaml &> %t.exe
|
|
RUN: llvm-bolt %t.exe -o %t.null --data %p/Inputs/blarge.fdata -v=2 \
|
|
RUN: --reorder-blocks=normal --print-finalized --log-file=%t.log 2>&1 \
|
|
RUN: | FileCheck --check-prefix=CHECK --allow-empty %s
|
|
RUN: FileCheck %s --check-prefix=CHECK-LOG --input-file %t.log
|
|
|
|
CHECK-NOT: BOLT-INFO
|
|
CHECK-NOT: BOLT-WARNING
|
|
CHECK-NOT: BOLT-ERROR
|
|
|
|
## Check some usual BOLT output lines are being redirected to the log file
|
|
CHECK-LOG: BOLT-INFO: Target architecture
|
|
CHECK-LOG: BOLT-INFO: BOLT version
|
|
CHECK-LOG: BOLT-INFO: basic block reordering modified layout
|
|
CHECK-LOG: Binary Function "main"
|