Regression run meta information - save to disk
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, tooling
Research direction
Start by tracing the regression-run flow and the code that creates its scratch directory and HTML summary report. Determine where run and job information first becomes available, then define the machine-readable metadata needed to link the regression run with its individual jobs. Done means the metadata is written early enough to remain useful when the overall run fails.
Written by the indexing model from the issue text.
Description
Once a run completes, there is no machine readable data linking the output of the run jobs with the regression run itself. The closest is the HTML summary report page that contains hyperlinks to the block level test reports.
Ideally we have a meta file in the scratch directory recording a regression run, and a reference to the individual jobs that were run as part of that regression run.
This should be generated as early in the flow as possible, so that the information can be used even if the overall regression run fails. This also opens up the potential for features such as continuing cancelled regression runs. Rerunning just the failed jobs, and other such features.
- Dominant language
- Python
- Stars
- 14
- Forks
- 21
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from lowRISC/dvsim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Better log visibility on the license type usage profilePossibly taken @AlexJones0 claimed this 6 days ago. Open
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 75/100
Similar issues
-
needs-human needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#2400 · 1 comment ·
Maintainers usually reply within 1 day
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/skywater-pdk#450 ·
-
Drained trajectory arrays are overwritten when the sequence buffer is reusedPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google-deepmind/bsuite#56 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LearningCircuit/local-deep-research#7206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day