"upload" only works with "compiled" benchmarks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 203
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 2
Description
My workflow for PyPy is
- download latest version compiled on buildbot,
- run benchmarks,
- upload data (using command line option
upload, which goes throughcompile.py, but should it?.
The cmd_upload function in compile.py assumes BenchmarkRevision.update_metadata from compile.py has been run to add commit information (commit_id, commit_branch, commit_date) and possibly patch_file to the json benchmark info. But because I am not running compile this info is lacking. Possible solutions:
- add a
download_prebuiltoption tocompile.pyand thePythonclass to support this workflow - refactor the
update_metadatamethod fromBenchmarkRevisionto become part of every benchmark run
Any thoughts? Should there be an upload.py separate from compile.py?
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
Start by reading compile.py, especially cmd_upload, BenchmarkRevision.update_metadata, and the Python class. Trace how downloaded buildbot benchmarks differ from compiled benchmarks and how metadata is added before upload. Done means the described PyPy workflow can upload benchmark data without requiring a local compile step, with the chosen separation or refactoring covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100