Closed
Bug 1508228
Opened 6 years ago
Closed 6 years ago
Weekly intermittent failures task fails due to being interrupted by daily dyno restart
Categories
(Tree Management :: Treeherder, defect, P1)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aryx, Assigned: sclements)
References
Details
Attachments
(1 file)
The weekly report (as bug comment) how often a bug got used for classification hasn't been added to every bug today (script failure in flight?).
Last week 1204 bugs got updated by the bot on Monday, this week only 265
Compare https://bugzilla.mozilla.org/page.cgi?id=user_activity.html&action=run&who=orangefactor%40bots.tld
with https://bugzilla.mozilla.org/page.cgi?id=user_activity.html&action=run&who=orangefactor%40bots.tld&from=2018-11-11&to=2018-11-13&group=when
Assignee | ||
Comment 1•6 years ago
|
||
I've manually run the task so they'll be 1200 comments (with some duplicates). The papertrail alert shows this error: WorkerLostError('Worker exited prematurely: signal 15 (SIGTERM).',). It looks like Heroku sends a SIGTERM to all processes when it's shutting down a dyno, which forces all the worker processes to immediately terminate. Not sure what a good work around is to prevent it from happening again - will look into it more.
Assignee | ||
Updated•6 years ago
|
Priority: -- → P1
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → sclements
Assignee | ||
Comment 2•6 years ago
|
||
Looking into this further, the Heroku Scheduler add-on could work as a replacement to the celery task. Since one of the options available is to run it daily, I could change the Commenter's default `weekly_mode` argument from False to a boolean check based on whether the current day is Monday (which will then run it in weekly or daily mode). The only caveat I see per the docs is: "Scheduler job execution is expected but not guaranteed. Scheduler is known to occasionally (but rarely) miss the execution of scheduled jobs." So then we'd still need to run it manually if that happened, assuming we'd get a papertrail alert. Ed, should we give this a try?
Flags: needinfo?(emorley)
Comment 3•6 years ago
|
||
Yeah I think it's the best option at the moment (and the move of other tasks to the scheduler addon in bug 1176492 has worked well so far).
Flags: needinfo?(emorley)
Assignee | ||
Updated•6 years ago
|
Status: NEW → ASSIGNED
Comment 4•6 years ago
|
||
Comment 5•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/24bda1ed838bf76011b227dde302d16a22d99ffb
Bug 1508228 - Remove Intermittents Commenter celery task (#4300)
Remove celery task and change Commenter weekly_mode default arg in
preparation for the move to the heroku scheduler
Comment 6•6 years ago
|
||
This is now deployed to production. Could you set up the scheduler tasks for prototype/stage/prod?
Flags: needinfo?(sclements)
Updated•6 years ago
|
Blocks: 1176492
Summary: Weekly intermittent failures summary report: not every bug used for classification updated → Weekly intermittent failures task fails due to being interrupted by daily dyno restart
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Intermittent Failures View → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•