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).
14 lines
694 B
C
14 lines
694 B
C
// RUN: %clang_analyze_cc1 -w -analyzer-checker=nullability \
|
|
// RUN: -analyzer-output=text -verify %s
|
|
//
|
|
// expected-no-diagnostics
|
|
//
|
|
// Previously there was an assertion requiring that if an Event is handled by
|
|
// some enabled checker, then there must be at least one enabled checker which
|
|
// can emit that kind of Event.
|
|
// This assertion failed when NullabilityChecker (which is a subclass of
|
|
// check::Event<ImplicitNullDerefEvent>) was enabled, but the checkers
|
|
// inheriting from EventDispatcher<ImplicitNullDerefEvent> were all disabled.
|
|
// This test file validates that enabling the nullability checkers (without any
|
|
// other checkers) no longer causes a crash.
|