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).
36 lines
1.8 KiB
C++
36 lines
1.8 KiB
C++
// RUN: rm -rf %t
|
|
// RUN: %clang_cc1 -fmodules -fmodules-cache-path=%t -fimplicit-module-maps -I%S/Inputs/suggest-include %s -verify
|
|
|
|
#include "empty.h" // import the module file
|
|
|
|
// expected-note@usetextual1.h:2 {{here}}
|
|
// expected-note@textual2.h:1 {{here}}
|
|
// expected-note@textual3.h:1 {{here}}
|
|
// expected-note@textual4.h:1 {{here}}
|
|
// expected-note@textual5.h:1 {{here}}
|
|
// expected-note@private1.h:1 {{here}}
|
|
// expected-note@private2.h:1 {{here}}
|
|
// expected-note@private3.h:1 {{here}}
|
|
|
|
void f() {
|
|
(void)::usetextual1; // expected-error {{missing '#include "usetextual1.h"'}}
|
|
(void)::usetextual2; // expected-error {{missing '#include "usetextual2.h"'}}
|
|
(void)::textual3; // expected-error-re {{{{^}}missing '#include "usetextual3.h"'}}
|
|
// If the declaration is in an include-guarded header, make sure we suggest
|
|
// including that rather than importing a module. In this case, there could
|
|
// be more than one module, and the module name we picked is almost certainly
|
|
// wrong.
|
|
(void)::textual4; // expected-error {{missing '#include "usetextual4.h"'; 'textual4' must be declared before it is used}}
|
|
(void)::textual5; // expected-error {{missing '#include "usetextual5.h"'; 'textual5' must be declared before it is used}}
|
|
|
|
// Don't suggest #including a private header.
|
|
// FIXME: We could suggest including "useprivate1.h" here, as it's the only
|
|
// public way to get at this declaration.
|
|
(void)::private1; // expected-error-re {{{{^}}declaration of 'private1'}}
|
|
// FIXME: Should we be suggesting an import at all here? Should declarations
|
|
// in private headers be visible when the surrounding module is imported?
|
|
(void)::private2; // expected-error-re {{{{^}}declaration of 'private2'}}
|
|
// Even if we suggest an include for private1, we should not do so here.
|
|
(void)::private3; // expected-error-re {{{{^}}declaration of 'private3'}}
|
|
}
|