[BUG] Manual build succeeds with final-pass typesetting warnings #3
Labels
No labels
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/docs#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The technical-manual build succeeds and publishes its PDF while the final TeX pass still emits underfull box diagnostics. This means a green manual job does not establish the required warning-free documentation result.
Reproduction
The observation is from one completed clean-checkout CI run at the exact revision below; this report did not rerun the compiler locally.
3beaff9142b46e5fdb1a4245aa629a90f0735b69indocs../scripts/build-manual.shwith fresh output directories.pdflatexpass and itsmain.log, then inspect the script's exit status.For isolated reproduction, set
BUILD_DIRandOUT_DIRto separate private directories before invoking the maintained script. Intermediate cross-reference warnings must be distinguished from diagnostics that survive the final pass.Expected and actual behavior
Expected: the final manual build has no warnings or layout diagnostics, and the validation gate rejects a final log that still contains them before copying/publishing the accepted PDF.
Actual: manual CI run 789, job
manual(job ID 19127, attempt 1), succeeded. Its third and finalpdflatexpass emitted 869 underfull horizontal-box and 14 underfull vertical-box diagnostics. The final pass had no overfull boxes and no remaining LaTeX unresolved-reference warnings. The resulting manual contains 1,825 pages.The maintained build script checks final-log overfull horizontal/vertical boxes but has no corresponding check for underfull diagnostics. Fix the source/layout causes and add final-log regression coverage; do not hide the diagnostics globally.
Environment and identity
erix/docsat3beaff9142b46e5fdb1a4245aa629a90f0735b69; exact main merge revision selected by run 789.Evidence and prior checks
The run 789 log records the third pass beginning at 05:34:17 UTC, final PDF generation at 05:35:28 UTC, and successful job completion. The first final-pass underfull diagnostic appears at 05:34:18 UTC. Read-only inspection retained the complete job log and separated final-pass counts from first/second-pass reference warnings.
Inspect
scripts/build-manual.shat the affected revision for the current overfull-only gate. No local compiler/VM was executed and no CI run was restarted or cancelled during this observation.The fix is published for review at signed commit
22d524bf234d5b205d543102d9e2d7dece2fe21din erix/docs#4. It corrects displayedAPI headings and prose/page/table layout and rejects nonempty final logs with
surviving diagnostics, missing logs, compiler failures and scanner failures.
No warning-threshold suppression is used. All 26 documentation tests pass.
The complete local maintained build exits 0 with 1,991 pages, zero final warnings,
all 5,715 API labels retained and zero out-of-page text among 379,275 checked word
boxes. Representative contents, prose, table and API pages were visually inspected.
PDF SHA-256:
70c3074aba101ad0c7ff79247152c7e57a6a06bf53c350ad3c60f812e9028d51.Earlier failed layout attempts remain separate evidence. Exact new-head CI is
still pending, so this issue remains open.
Tracking
Closure needs source/layout corrections, a final-log gate regression that rejects underfull diagnostics, warning-free complete manual generation at the changed revision, and inspection of affected rendered pages. Keep early-pass reference resolution and final-pass acceptance separate.
Related documentation work: inline documentation and warning-free builds and documentation repository audit.
erikinkinen referenced this issue2026-09-12 08:28:22 +02:00
erikinkinen referenced this issue2026-09-15 06:45:36 +02:00