Open Bug 1704135 Opened 3 years ago Updated 3 years ago

Send an email when try decision task fails

Categories

(Tree Management :: Treeherder, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: u608768, Unassigned)

Details

My workflow is something like:

  1. Make some changes and push to try
  2. Check the results after 1-3 hours, depending on the size of the push

I seldom check the results immediately after pushing.

Now if the push had an intermittent decision task failure (eg like in https://treeherder.mozilla.org/jobs?repo=try&revision=9f84ffcf6abe024cd28b8a7d5f7ff91fc7ba1b1f), I end up having to push again and waiting another 1-3 hours (sometimes more). This has happened a few times to me.

So I'm wondering if it's possible to email the user that there was a decision task failure (which will notify them within a few minutes of making the push), so they can know to push again. Maybe it's possible to even delay the "thank you for your submission" email until the decision task has passed, and just bundle the "decision task failed/passed" notification with that email?

Hm, I think I do receive taskcluster failure emails.

These look like:

From: firefoxcitc-taskcluster-noreply@mozilla.com via amazonses.com 
Subject: Task failed: Gecko Decision Task - URi4NDkVRZ-y8YTBBFnw2Q

and if I look at a try decision task's task definition, I see routes like

	"notify.email.asasaki@mozilla.com.on-failed"
	"notify.email.asasaki@mozilla.com.on-exception"
	"notify.email.asasaki@mozilla.com.on-completed"

Have you checked your spam folder?

Looking at your try push, your decision task has

"notify.email.kmadan@mozilla.com.on-failed"
"notify.email.kmadan@mozilla.com.on-exception"
"notify.email.kmadan@mozilla.com.on-completed"

Oh, weird. The only emails I see from taskcluster are the "Thank you for your try submission of ..." ones. Spam has nothing as well.

Edit: I've received one such email in the past for this autoland push: https://treeherder.mozilla.org/jobs?repo=autoland&revision=0dadbfb3feca4bbc00a4d8cfe87dd6ab2f59a643

You need to log in before you can comment on or make changes to this bug.