other than notarization poller, scriptworkers don't respect max run time

Open
#720 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devops

Research direction

Start by tracing how scriptworkers enforce the configured max run time, using the linked task as a reproduction example. Compare the behavior with the notarization poller, which is noted as an exception, and inspect how the task is terminated with signal -15. Done means scriptworker tasks stop near their configured limit instead of running substantially longer.

Written by the indexing model from the issue text.

Description

We've found a few examples of tasks going well over their max run time recently. For example, this task had a max run time of 600 seconds (10 minutes). The first attempt ran for 21 minutes, after which it was killed with signal -15. The second run ran for 16 minutes and completed successfully.

It's possible the first one was killed for going over the max run time -- but even if that's the case, that's far too late.

Dominant language
Python
Stars
16
Forks
38
Avg merge
1d 7h
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-releng/scriptworker-scripts

All issues in mozilla-releng/scriptworker-scripts

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.