Closed Bug 771756 Opened 12 years ago Closed 12 years ago

Stop running talos on Android XUL

Categories

(Release Engineering :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Whiteboard: [capacity])

Attachments

(2 files)

The same story as bug 771421 - the only people who have any interest in Android XUL are b2g, and they are only interested in keeping OOP alive until they get their own tests running, so mochitests and maybe C/J/R. Nobody wants to see XUL talos anymore, especially not the tegra pool that has to run it. "<mfinkle>: worth filing a bug to shut XUL talos down"
From our last Mobile:Testing meeting (June 27) this was discussed and determined that we could not shut down testing for Android XUL until we get win8 testing up and running properly. I'll make sure we talk about this again this coming week.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Currently seeing a lot of backlog on android tests, a la bug 772458.
Blocks: 772458
Callek, re comment 1: not even just talos?
I believe disabling talos for XUL should be the right thing to do. Blassey ^? consent?
reopening because we eventually want to stop running tests on XUL fennec. As I understand it these tests are useful to B2G because they test e10s and the Metro work because they test similar XUL code. Once those teams/projects have their testing up to snuff we should turn these tests off. So, to summarize, from the mobile team's perspective go ahead and turn them off. We should get sign off from desktop (for the Metro testing, Asa is already aware of this) and B2G that they no longer need XUL fennec as a proxy for their testing. Adding Asa and cjones to the CC so they can comment.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
In this bug, we're specifically asking about *talos/performace* rather than unit testing. I don't there should be any inconvenience on stopping to measure the performance of a product that we don't ship anymore. I assume we want to keep talos performance for mozilla-beta/mozilla-release since we're still shipping the XUL version for tablets; correct?
(In reply to Brad Lassey [:blassey] from comment #5) > reopening because we eventually want to stop running tests on XUL fennec. As > I understand it these tests are useful to B2G because they test e10s and the > Metro work because they test similar XUL code. Once those teams/projects > have their testing up to snuff we should turn these tests off. FWIW, Metro front end code (which is a fork of XUL Fennec front end) moved to browser/metro and is already undergoing major changes. So the Fennec XUL tests in /mobile no longer matter to us.
xul-fennec talos tests are not useful for b2g.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #8) > xul-fennec talos tests are not useful for b2g. Are xul fennec unit tests useful for b2g?
Ran test-masters and reconfiged my test staging master with it. Android XUL unit tests stayed; Android XUL talos disappeared.
Attachment #640808 - Flags: review?(armenzg)
(In reply to Aki Sasaki [:aki] from comment #9) > (In reply to Chris Jones [:cjones] [:warhammer] from comment #8) > > xul-fennec talos tests are not useful for b2g. > > Are xul fennec unit tests useful for b2g? reftests are useful because we don't have those running on b2g yet. Hopefully soon. We had mochitests running but now hit a problem so the xul-fennec ones are temporarily useful again.
Does that include crashtest and jsreftest? Sounds like we can reopen bug 771421 at least and turn off android-xul browser-chrome.
crashtest is useful while reftest harness not spun up for b2g. jsreftest useful but less so.
Comment on attachment 640808 [details] [diff] [review] remove android-xul from talos Review of attachment 640808 [details] [diff] [review]: ----------------------------------------------------------------- I will attach the diff of builder_list.py ftr.
Attachment #640808 - Flags: review?(armenzg) → review+
Blocks: 772928
This made it to production today.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: