CI Bench

CI Bench

Submit a correction or a configuration

By issue or pull request on the repository. Rules: CONTRIBUTING.md.

Report an error
Open an issue: result set, cell, what is wrong (configuration, price, billing rule, portability edit). Answer within 5 business days. An accepted correction goes in the result set's errata.md with recomputed files and a date on the changelog; raw job records never change. A declined report gets its reason. Reports about Vitko's own results are not closed without a second reviewer.
Submit runs
Pull request adding submissions/<date>-<provider>/: the collect.py output from runs in a public repository, providers/<id>.json with the price source, and your plan. CI recomputes the summaries from the raw records. Shown as “submitted, not reproduced” until an official round reproduces them; never mixed into official indices.
Add a configuration
providers/<id>.json with the runs-on label, size, public price URL, billing rule, the plan a new customer would use, setup steps, and a link showing the provider’s terms allow publishing benchmark results. Include a submitted run. It joins official rounds from the next one.
Right of reply
A measured provider can report an error by issue or at benchmark@vitko.inc. Corrections are published with their date.