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).
15 lines
421 B
Fortran
15 lines
421 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1
|
|
|
|
! Ensure that spurious errors do not arise from FinishSpecificationPart
|
|
! checking on a nested specification part.
|
|
real, save :: x
|
|
interface
|
|
subroutine subr(x)
|
|
real, intent(in) :: x
|
|
! SAVE attribute checking should not complain at the
|
|
! end of this specification part about a dummy argument
|
|
! having the SAVE attribute.
|
|
end subroutine
|
|
end interface
|
|
end
|