Publish raw benchmark results
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 4
Description
One rather intricate solution is to make a website:
Each check run’s details tab has a link that reads “View more details on scverse-benchmark”. Without overriding it, it links to the GH app’s public URL, which currently goes nowhere useful.
We could make the official bot URL point to the website and override an individual run’s link using the details_url body parameter to link to subpage that provides a run’s JSON for download.
A simpler option would be to use the “update a check run” endpoint’s output.annotations[].raw_details, which can contain 64 kb of data and is rendered like this:
It wouldn’t be a great fit, as it’s attached to a certain file, but the only field that is explicitly for bigger data than a line or so.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by comparing the proposed website with GitHub's update-a-check-run endpoint and its raw_details field; done means a check-run details link or annotation exposes the benchmark run's raw JSON for download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100