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).
30 lines
513 B
Fortran
30 lines
513 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1
|
|
program main
|
|
|
|
integer j, k
|
|
|
|
lab1: do j=1,10
|
|
cycle lab1
|
|
exit lab1
|
|
end do lab1
|
|
|
|
lab2: do 2 j=1,10
|
|
cycle lab2
|
|
exit lab2
|
|
2 end do lab2
|
|
|
|
lab3: do 3 j=1,10
|
|
cycle lab3
|
|
exit lab3
|
|
!ERROR: DO construct name required but missing
|
|
3 end do
|
|
|
|
do 4 j=1,10
|
|
!ERROR: Unexpected DO construct name 'lab4'
|
|
4 end do lab4
|
|
|
|
lab5: do 5 j=1,10
|
|
!ERROR: END DO statement must have the label '5' matching its DO statement
|
|
666 end do lab5
|
|
end
|