Repository navigation
Run all BenchmarkDotNet cases in parallel CI jobs - #4
Merged
Merged
Conversation
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 serial GitHub Actions job hit its 180-minute limit after ten of 23 cases. The ordinary 10,000-tool catalog took 32m 31s to initialize. CI now derives ten independent jobs from BenchmarkDotNet discovery and checks the identity, timing and allocations of every case. Each job uploads its reports. The suite uses the original fixtures, DefaultJob and MemoryDiagnoser.
This PR also adopts the public ManagedCode.MarkdownLd.Kb 0.3.1 package. The NuGet DLL matches the GitHub release asset and the consumer's resolved dependency. The owner repair preserves the complete ordered graph relations and reduces redundant work during catalog construction.
The two measurements used different hosted Linux runners. The new warm discovery, schema and invocation cycle averaged 37.57 seconds and allocated 38.17 GiB per operation. The owner review isolates the SPARQL evidence and provenance cost.
Verification includes 456 passing tests locally and on Linux, 92.48% Linux line coverage, a clean formatting check, CodeQL, and a vulnerability scan with zero advisories. The exact Linux CI run completed in about 61 minutes. All 23 unique full JSON reports across ten jobs contain numeric timings and allocations. The original timed-out job and the new ordinary 10,000-tool job retain the original measurements.