Skip to content

Contribute compile times to cratebank - #36

Open
zmaril wants to merge 2 commits into
mainfrom
cratebank-census
Open

Contribute compile times to cratebank#36
zmaril wants to merge 2 commits into
mainfrom
cratebank-census

Conversation

@zmaril

@zmaril zmaril commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Adds this repository to the public compile-time census at https://cratebank.io/, on every CI run rather than on a schedule.

The step goes into the existing gate job, before the cargo steps, and builds what they would have built anyway — so the added cost is mostly the measuring rather than a second build, since the steps below reuse the target directory.

The opt-in

[…metadata.cratebank]
public = true
repository = "https://github.com/PowderworksCode/straitjacket"

Without it the census records the build and withholds this repository's own crate names. They are already public here. Measured on entl: 243 units with 7 withheld → 250 with 0, and the repository URL recorded.

strict: true

This is the build now. A measurement that quietly did not happen would mean nothing built the project either, and a green check would be saying so about work that never ran. Elsewhere strict defaults to false, because a census that breaks builds is a census people switch off; here the build is the thing being measured, so silence is the worse failure.

Cost

Two fixes landed in cratebank first, because doing this on every CI run rather than weekly changes what the overhead is worth:

before after
samply install 125s, built from source ~1s, prebuilt and checksummed
client install ~90s, built from source prebuilt archive for the pinned tag

The action step measured 244s before those and 127s after the first.

Untested here

This has never run in this repository. The first CI run on this pull request is the real test.

🤖 Generated with Claude Code

https://claude.ai/code/session_01361quprG7tUgaVFKAmKtJZ

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 25, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
straitjacket 985f289 Commit Preview URL

Branch Preview URL
Aug 25 2026, 08:37 PM

The build this job already runs, measured, plus the opt-in that lets
this repository's crate names appear in the census rather than a count.
They are already public here.

It goes before the existing cargo steps and builds what they would have
built, so the added cost is mostly the measuring rather than a second
build. `strict` is on, because this is the build now: a measurement that
quietly did not happen would mean nothing built the project either.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01361quprG7tUgaVFKAmKtJZ
The opt-in arrived with three lines of comment explaining it, and this
repository's own `no-comments` rule caught them: ordinary comments
outside the leading ten-line file header, in a manifest that does not
have one.

    Cargo.toml:N  [no-comments]  # Opted in: this repository is public...

The rule is right. The reasoning belongs where someone reviewing the
change reads it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant