Intermittent browser/base/content/test/alerts/browser_notification_replace.js | Test timed out -
Categories
(Core :: DOM: Push Subscriptions, defect, P3)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [stockwell disabled])
| Comment hidden (Intermittent Failures Robot) |
Comment 2•8 years ago
|
||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 10•8 years ago
|
||
Comment 11•8 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•8 years ago
|
Comment 14•8 years ago
|
||
| bugherder uplift | ||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 17•8 years ago
|
||
Updated•7 years ago
|
Comment 19•6 years ago
|
||
Hey MattN,
This has been P1 for a few years with no activity. I'm going to move it back to a P3... if we decide to make it a P1 again, who would you recommend for an assignee?
Comment 20•6 years ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #19)
This has been P1 for a few years with no activity. I'm going to move it back to a P3...
I am not in charge of resourcing, I'm just the triage owner, so it's not my fault that there was no activity. Management should be assigning resources based on priority and I already escalated this (with the related tests) years ago and it got assigned to mdeboer's team but they never fixed any. This is testing functionality shipping for all users and now has no test coverage so from the perspective of this component it is one of the most important things to fix before any new work goes on for the alerts service.
if we decide to make it a P1 again, who would you recommend for an assignee?
Any Firefox front-end dev could fix this.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Comment 21•2 years ago
|
||
(This is indeed a DOM test that should not actually be in browser/base/content/.)
Comment 22•2 years ago
|
||
But this seems inactive.
Updated•2 years ago
|
Description
•