Repository navigation
ci-fresh-install: each toolchain of the Linux fresh install is a job of its own - #978
Open
Sunrisepeak wants to merge 1 commit into
Open
Sunrisepeak wants to merge 1 commit into
Sunrisepeak wants to merge 1 commit into
Conversation
…of its own The Linux fresh install built mcpp four times in one job: the default toolchain, musl-gcc, gcc 16 and LLVM. The builds of 2026.11.19.1 took 17.9, 18.0, 15.8 and more than 6.6 min after the release (run 44634649039), against 9.9 to 12.8 min each for 2026.11.18.1, and the job reached its 60 min during the fourth. The longest unit is now src/build/prepare/graph.cpp at 4 min 52 s, against platform.cpp at 3 min 20 s. Each toolchain is now a leg of a matrix that installs the release on a fresh machine, makes the toolchain the default, builds and runs a new project, and builds and runs mcpp, within 45 min. The template fetch runs on the default leg. A user who installs one toolchain sees what its leg sees; the legs no longer share a home.
This branch has not been deployed
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 fresh install built mcpp four times in one job (the default toolchain, musl-gcc, gcc 16, LLVM). After the 2026.11.19.1 release the builds took 17.9, 18.0, 15.8 and more than 6.6 min (run 44634649039), against 9.9 to 12.8 min each for 2026.11.18.1 (runs 44228343834, 44555477643), and the job reached its 60 min during the fourth build. Every other leg of that run passed, the arch and Termux app sandbox legs fixed in #966 among them.
The time went to compilation, not to the engine or to downloads: the jobs downloaded from github.com (GLOBAL), the longest unit is now
src/build/prepare/graph.cppat 4 min 52 s (platform.cppat 3 min 20 s for 2026.11.18.1), and locally the 19.1 tree plans 826 compile commands under both engines and builds in 158 s under 2026.11.18.1 and 155 s under 2026.11.19.1.Each toolchain is now a leg of a matrix that installs the release on a fresh machine, makes the toolchain the default, builds and runs a new project, and builds and runs mcpp, within 45 min; the template fetch runs on the default leg. The legs no longer share a home, so each sees what a user who installs that one toolchain sees.
After the merge,
ci-fresh-installis dispatched on main to verify 2026.11.19.1 on every leg.