Repository navigation
Reduce Linux lifetime build memory and log coverage job resource use - #301
Merged
Merged
Conversation
Compile the DIP1000 suite one module per compiler invocation and limit DUB to two workers using the runner's allowed CPU set. Local package builds peaked near 14.9 GiB. With two workers, sampled compiler memory peaked at 2.8–3.4 GiB and all 90 modules passed in under three minutes. Run both Linux lifetime jobs through the existing resource logger to capture timing and memory samples. The LDC package build provides a baseline for evaluating per-file compilation on hosted runners. AI-Assisted-By: Codex (GPT-6 Astra Medium)
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Compile the DIP1000 suite one module per invocation and limit DUB to four workers from the runner's allowed CPU set. Use the same affinity selection as the Linux LDC release job. In local clean builds, four workers reduced elapsed time from 3m 29s to 2m 30s and peak sampled compiler memory from 14.90 GiB to 5.63 GiB. Both builds passed all 90 modules. AI-Assisted-By: Codex (GPT-6 Astra Medium)
Run Linux DMD and LDC general coverage, Linux BLAS coverage, and the Linux LDC slow numerical suite through the existing resource logger. Use the Windows resource logger for LDC general coverage. Capture memory samples during compilation and test execution to help diagnose runner disconnects. Preserve the existing DUB build modes, coverage report handling, and test exit codes. AI-Assisted-By: Codex (GPT-6 Astra Medium)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Linux DMD DIP1000 lifetime jobs on #277 and #283 lost contact with their hosted runners and passed on retry. Local DMD package builds peaked near 14.9 GiB on both PRs and their common base. The cause of the disconnects remains unconfirmed.
Build the Linux DIP1000 lifetime suite one module per compiler invocation. DUB uses up to two workers for DMD and four for LDC, selected from the runner’s allowed CPUs. Both jobs log elapsed time and sample memory every 30 seconds.
Extend the same diagnostics to Linux DMD and LDC general coverage, Windows LDC general coverage, Linux BLAS coverage, and the Linux LDC slow-numerics suite. These steps retain their existing DUB build modes and coverage report handling.
Validation
Local DMD two-worker builds passed all 90 modules on #277 and #283 with peak sampled compiler memory of 3.4 GiB and 2.8 GiB, respectively. For LDC, four workers reduced local build and test time from 3m 29s to 2m 30s and peak sampled compiler memory from 14.90 GiB to 5.63 GiB.
All 22 checks passed on the final PR head. The hosted Linux lifetime steps passed all 90 modules in 1m 51s with DMD and 3m 01s with LDC. The new logs also showed that Linux general coverage still peaked at 14.77 GiB for both compilers. Final CI run
AI-Assisted-By: Codex (GPT-6 Astra Medium)