Disable all browser-chrome tests on debug due to bug 1546945
Categories
(Remote Protocol :: Agent, defect, P1)
Tracking
(Not tracked)
People
(Reporter: ato, Assigned: ato)
References
Details
Attachments
(2 files)
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Before landing the remote agent in Firefox Nightly, we had to disable
remote/test/browser/browser_cdp.js because it caused a permafailure
on debug due to a memory leak. We thought the problem was limited
to this specific test, but over the weekend two more intermittent
leaks were discovered:
- https://bugzilla.mozilla.org/show_bug.cgi?id=1546850
- https://bugzilla.mozilla.org/show_bug.cgi?id=1547303
Until we have had time to investigate and plug the leak, we will
disable all the browser-chrome tests on all debug platforms.
Comment 3•6 years ago
|
||
Please also disable them in ASan (Bug 1547303 is a leak detected by LeakSanitizer, which is run as part of AddressSanitizer.)
Assignee | ||
Comment 4•6 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #3)
Please also disable them in ASan (Bug 1547303 is a leak detected
by LeakSanitizer, which is run as part of AddressSanitizer.)
Thanks for the head’s up!
I actually asked about this in meeting we had earlier today, about
why we hadn’t seen any fallouts in ASan jobs. I just assumed I
had misunderstood what ASan was about, but glad you confirmed my
original idea was the right one.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 5•6 years ago
|
||
bugherder |
Assignee | ||
Comment 6•6 years ago
|
||
We should also disable browser-chrome tests on ASan, as some of
the leaks reported were caught by LeakSanitizer, which is run as
part of AddressSanitizer.
Follow-up from https://bugzilla.mozilla.org/show_bug.cgi?id=1547679#c3.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 8•6 years ago
|
||
bugherder |
Description
•