Closed Bug 1365054 Opened 7 years ago Closed 7 years ago

Intermittent test_system_update.js | - A promise chain failed to handle a rejection: can't convert undefined to object - rejection date: Mon May 15 2017 04:41:58 GMT-0700 (Pacific Standard Time) - stack: _do_main@head.js:211:5

Categories

(Toolkit :: Add-ons Manager, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])

this is a consistent failure right below the threshold for stockwell to look into, windows 8 debug specifically.  I am not sure if there is any simple fixes here- possibly a quick look would help?
Flags: needinfo?(amckay)
08:51:40  WARNING -  TEST-UNEXPECTED-FAIL | xpcshell.ini:toolkit/mozapps/extensions/test/xpcshell/test_system_update.js |  - A promise chain failed to handle a rejection: can't convert undefined to object - rejection date: Sat Jul 01 2017 08:51:11 GMT-0700 (Pacific Standard Time) - stack: _do_main@C:\\slave\\test\\build\\tests\\xpcshell\\head.js:220:3

Since Thu Jun 29, 2017, 18:36:46
https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=2983f04886b61661fc69d2eb5262084f902e0486

this is a perma-failure on Windows debug in the Thunderbird Xpcshell test run.
we had many failures last week, but as of July 11th this seems to have reduced significantly.
Whiteboard: [stockwell unknown]
Flags: needinfo?(amckay) → needinfo?(bob.silverberg)
Joel, this was frequent a few months ago, but over the past couple of months it's down to 1 failure per week (or less), so I am marking it as a P5 and removing the [stockwell unknown] flag. Does that seem like the correct action to take at this time?
Flags: needinfo?(bob.silverberg) → needinfo?(jmaher)
Priority: -- → P5
Whiteboard: [stockwell unknown]
I actually leave [stockwell unknown] as it helps find bugs that 'magically fixed themselves'.  While we don't do much with them, it does provide an interesting metric as to how many bugs are a priority at one point in time, then not in the future with no clear cause as to the fix.  P5 is a great action here, and I think even closing this bug would be reasonable since it has been a month with no instances, and back then it was only on mozilla-release.
Flags: needinfo?(jmaher)
Whiteboard: [stockwell unknown]
Thanks Joel, what resolution would I use if I want to close it?
we have been using INCOMPLETE or WORKSFORME- hopefully the list is small- we typically say 3 weeks with no failures and we can resolve an intermittent bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.