Save each job spec to the scratch directory
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 21
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
Prior to calling the scheduler, save each individual JobSpec object to the scratch directory. This provides a useful debugging checkpoint, and opens up a number of potential new features... such as pausing and resuming regressions, retrying failed jobs due to transient issues (license availability).
Contributor 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.
Research direction
Trace the scheduler invocation and the JobSpec handling in the DVSim codebase, then identify how the scratch directory is selected. Verify the behavior for a run containing multiple JobSpec objects and confirm that each object is saved before its job is submitted to the scheduler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100