show average build durations in build lists, crate details #3134
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
github-actions
bot
added
the
S-waiting-on-review
syphar
force-pushed
the
show-build-duration
branch
from
a350fa4 to
a2eeb77
Compare
syphar
force-pushed
the
show-build-duration
branch
from
a2eeb77 to
89fd600
Compare
GuillaumeGomez
approved these changes
Jan 12, 2026
Member
|
Thanks! :) |
github-actions
bot
added
S-waiting-on-deploy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This shows the build duration in the build-list for a release, and an average duration (this release or all release) in the crate-details page.
I've put logic into database views for some of the future things I want to do with this.
note: there were some html errors in
crate/builds.htmlI just fixed in this PR.next things after this PR
My idea is, if it works performance wise, to add a column to the build queue where you see an estimated build-time for each entry. Logic would be to just start at the first entry, current time, and add up the historical averages for the crate to estimate the build time for each new release.
We could also show some ecosystem wide statistics to users, or crate-level graphs to the crate authors (like, historical build durations for your crate).