Record the M3.10b merge facts and the matrix margin - #174
Merged
Conversation
The handoff named the run and the margin as "recorded below" before either existed, because the slice's own commits could not carry the result of the run that verified them. Both are now exact: the candidate at `66fcab8` and the post-merge run on `cc2e8fc`, with per-job durations on each. The margin is about ten and a half minutes and the slice moved it very little, which is the expected result for a change that adds no translation unit. The figure is recorded so M3.10c has a baseline, because that slice is C++ and build time is the larger half of each job.
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
1 participant
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.
Documentation only. The M3.10b handoff named its verification run and its margin as "recorded below" before either existed, because the slice's own commits could not carry the result of the run that verified them.
Both are now exact:
66fcab8passed the complete hosted matrix — scope classificationfull, GCC and Clang debug, both sanitizers, and the aggregate required check.cc2e8fcpassed the same matrix.gcc-debug5m48s,clang-sanitizers7m21s,clang-debug8m45s,gcc-sanitizers9m21s. Post-merge:clang-debug8m15s,gcc-debug8m17s,clang-sanitizers8m50s,gcc-sanitizers9m20s.The margin is about ten and a half minutes and the slice moved it very little, which is expected for a change that adds no translation unit and two fast Python entries
ctest --parallelabsorbs. The spread between the two runs sits inside the roughly 12% run-to-run variance M3.7a measured on identical code. The figure is recorded so M3.10c has a baseline, because that slice is C++ and build time is the larger half of each job.Takes the focused metadata verification path: the diff is one Markdown file.