Repository navigation
test: case 860 holds the members' build programs under way together by their steps - #1000
Merged
Merged
Conversation
…y their steps, not by when their compiles fall
…e deployment written for every member is no member's
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.
Case
workspace/graph/860asserted that at-j 4at least two members' build programs compile at the same time. In run 44959494484 (macOS, three processors) it failed and passed on a re-run: each compile waits for its own unit's scan, the scans of the same file took 0.19, 1.65 and 2.75 s, and the compiles (0.7 to 0.9 s each) fell one after another. Whether compiles overlap follows from the scans' times; what the build graph holds is that the members' build programs advance together in one graph, and the scans of all three members began within 35 ms of the graph's start.-j 4, steps of at least two members (scan, compile, resource, link:obj/<m>-…,res/<m>-…,bin/<m>-…of the build programs'.ninja_log) are under way at one instant; each member's compile is recorded.-j 1, one member at a time (stronger than one compile at a time).-j 1read as three members at once, run 44988440716).Test-only; the engine is unchanged.