Add new fields to display the actual start and end times of Hackbot runs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the Hackbot run model or API entry point that exposes created_at and finalized_at, then trace where provisioning and agent execution timestamps are available. The work is done when new fields expose the actual agent start and end times separately from request creation and finalization, with relevant tests updated or added.
Written by the indexing model from the issue text.
Description
The created_at field reflects the time for when the run was requested, not when the agent started, which does not reflect the delay for provisioning the execution environment. Similarly, the finalized_at reflects the time when we finalized the run, which can be delayed due to error and retry, see https://github.com/mozilla/bugbug/issues/6691#issuecomment-5417559947.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
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.
More from mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100