The default bug view has changed. See this FAQ.

Consider fully disabling mochitest-bc and mochitest-dt on the B2G release branches

RESOLVED FIXED

Status

Release Engineering
Release Automation
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: RyanVM, Assigned: massimo)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [capacity])

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
Do we get any useful test coverage by running the browser-chrome and devtools mochitests on the B2G release branches(b2g28, b2g30, b2g32)? We don't ship any browser builds from those branches and IIUC, the tests really don't cover much in the way of B2G functionality.

To cut down on wasted load and intermittent oranges that aren't likely to be fixed, I'd like to shut them off if they don't serve any useful purpose.
(Reporter)

Comment 1

3 years ago
Rob/Gavin, I guess I'm really looking for your feedback on this. Feel free to loop in any others you want to weigh in.
Flags: needinfo?(rcampbell)
Flags: needinfo?(gavin.sharp)
I'll defer to Paul. He's more looped-in to the B2G testing universe.
Flags: needinfo?(rcampbell) → needinfo?(paul)

Comment 3

3 years ago
Alex knows these things (he's on holiday, coming back next week).
Flags: needinfo?(paul) → needinfo?(apoirot)
As far as I know there is no b2g coverage in any browser-chrome tests, though I suppose in theory there could be some coverage of Gecko features. Probably not any that b2g depends on that it doesn't have its own coverage for, though, and if we're not shipping browser builds from those branches I see little point in running browser-chrome tests.
Flags: needinfo?(gavin.sharp)
There isn't any b2g specific tests in browser-* suites.
But as gavin said, there can still be some useful platform tests, that aren't testing anything related to browser chrome. Instead they focus on some lower level platform code.
There shouldn't be many, but I know at least one or two related to webapps API.
  http://mxr.mozilla.org/mozilla-central/source/dom/tests/browser/browser.ini#33
But it looks like they are disabled.

At the end I would say that there is a quite limited value in running them on b2g branches.
Regarding browser-devtools, I think there is absolutely no value in running them.

We may introduce some new kind of browser-* suite once Mulet is ready where we would test some b2g specifics.
It will allow us to test in the same suite browser chrome client code against b2g remote debugging server.
Flags: needinfo?(apoirot)
(Reporter)

Comment 6

3 years ago
This is probably past my ability to drive forward at this point. James, might you be able to help here?
Flags: needinfo?(jlal)
Heh "absolutely no value" to me means lets turn them off :)
Flags: needinfo?(jlal)
(Reporter)

Comment 8

3 years ago
I was asking for someone to write the patch ;)
Flags: needinfo?(jlal)

Updated

3 years ago
Assignee: nobody → mgervasini
Flags: needinfo?(jlal)
(Assignee)

Comment 9

3 years ago
Created attachment 8479972 [details] [diff] [review]
[buildbot-configs] Bug 1045398 - disabling mochitest-bc and mochitest-dt on the B2G release branches.patch

Removes mochitest-devtools-chrome and mochitest-browser-chrome from mozilla-b2g* branches
Attachment #8479972 - Flags: review?(catlee)
(Assignee)

Comment 10

3 years ago
Created attachment 8479974 [details]
differences

and this is the list of removed builders
Attachment #8479974 - Flags: feedback?(catlee)

Updated

3 years ago
Attachment #8479972 - Flags: review?(catlee) → review+

Updated

3 years ago
Attachment #8479974 - Flags: feedback?(catlee) → feedback+
(Assignee)

Updated

3 years ago
Attachment #8479972 - Flags: checked-in+
bbot-cfg patch is in production
(Reporter)

Comment 12

3 years ago
And working perfectly, thanks!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.