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
918 B
C++
22 lines
918 B
C++
// REQUIRES: host-supports-jit
|
|
// UNSUPPORTED: system-aix
|
|
// clang-repl can be called from the prompt in non-interactive mode as a
|
|
// calculator in shell scripts, for example. In that case if there is an error
|
|
// we should set the exit code as failure.
|
|
// RUN: not clang-repl "int x = 10;" "int y=7; err;" "int y = 10;"
|
|
|
|
// In interactive (REPL) mode, we can have errors but we should exit with
|
|
// success because errors in the input code are part of the interactive use.
|
|
// RUN: cat %s | clang-repl | FileCheck %s
|
|
|
|
// However, interactive mode should fail when we specified -verify and there
|
|
// was a diagnostic mismatches. This will make the testsuite fail as intended.
|
|
// RUN: cat %s | not clang-repl -Xcc -Xclang -Xcc -verify | FileCheck %s
|
|
|
|
BOOM! // expected-error {{intended to fail the -verify test}}
|
|
extern "C" int printf(const char *, ...);
|
|
int i = 42;
|
|
auto r1 = printf("i = %d\n", i);
|
|
// CHECK: i = 42
|
|
%quit
|