Timing data in Job objects
Open
- Dominant language
- Python
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
After jobs are done, should be able to get at least the walltime of the job
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the Job objects and the lifecycle of a completed job. Determine where completion data is stored or exposed, then make the walltime available after a job finishes and verify it through the existing job-management checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100