Repository navigation
Add weekly runner samples and daily dependency comparisons - #76
Merged
Merged
Conversation
Serialize samples with rolling builds, retain source and operation metadata, and restore native Namespace and Blacksmith cache lanes. Fix the Bundler INSTALL environment collision and require complete dependency cycles for timings. Provider setup: https://namespace.so/docs/reference/github-actions/nscloud-cache-action and https://github.com/useblacksmith/setup-docker-builder Validation: 148 tests and 487 assertions passed; subsequent report and post-job timing checks passed 52 tests and 139 assertions. Catalog check, actionlint and whitespace checks pass.
gauravtiwari
marked this pull request as ready for review
October 19, 2026 13:33
gauravtiwari
force-pushed
the
runner-samples
branch
from
October 19, 2026 14:34
03462bf to
07b678f
Compare
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.
Regular GitHub builds continue producing the rolling cache. Weekly PostHog/Depot, Zed/Namespace and Chroma/Blacksmith samples now rebuild the latest completed GitHub source commit, with a GitHub control, under the same project concurrency group. Samples also run when upstream has no new commit and do not advance rolling. Native Namespace volumes and Blacksmith Docker caching are included; manual samples accept configured larger runners.
Daily dependency jobs rotate one case across four providers and add cross-provider restores where the cache backend permits them. The report requires complete passing install/update/verify cycles, records source and consumer CPU separately, and keeps runner samples separate from rolling medians. The Bundler harness no longer exports Autoconf's reserved INSTALL variable. Missing post-job save timings remain unmeasured.
Internal product investigation and operations notes are removed from the current tree and Git history. Benchmark measurements and customer-accessible CLI/action evidence are retained.
Validation: 148 tests pass, along with catalog validation, actionlint and whitespace checks. Hosted Discourse Bundler qualification passed all 28 measurements. The complete dependency comparison passed all 112 measurements across four cases and four runner providers. Both runs are recorded in deps/results and data/deps.md.
Measurement limits are in tools/README.md and docs/results.md. The Namespace volume runner and existing BoringCache profile differ in configured swap. Native weekly cache histories and BoringCache's completed GitHub cache are different usage patterns; the report does not calculate a cache-only speedup between them. Hosted build qualification and default-branch schedule activation remain pending.
Provider setup follows Namespace's cache action and Blacksmith's Docker builder action.