Closed Bug 777037 Opened 12 years ago Closed 12 years ago

Stop doing android-xul builds/unittest/talos where no longer needed

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 774424

People

(Reporter: joduinn, Unassigned)

References

Details

per mtg w/blassey:

The android-xul builds, unittests and talos are no longer needed since transition to nativefennec, and these are using up android compute time that we can use better elsewhere. Therefore:

1) Leave android-xul builds and unittests on for mozilla-inbound, mozilla-central. Per bug#771756#c11, this is enough as interim for B2G developers. 
2) Disable android-xul builds, unittests and talos on all other branches (includes all project branches, mozilla-aurora/beta/releases)
3) bug#750285 tracks turning off as default on try
Related: bug 774424 which turns it all off by Aug 27.
Blocks: 772458
Is this a dupe of 750285?
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #2)
> Is this a dupe of 750285?

No, I think this bug also covers turning android-xul off on beta, release, and project branches.
(In reply to John O'Duinn [:joduinn] from comment #0)
> per mtg w/blassey:
> 
> The android-xul builds, unittests and talos are no longer needed since
> transition to nativefennec, and these are using up android compute time that
> we can use better elsewhere. Therefore:
> 
> 1) Leave android-xul builds and unittests on for mozilla-inbound,
> mozilla-central. Per bug#771756#c11, this is enough as interim for B2G
> developers.
> 2) Disable android-xul builds, unittests and talos on all other branches
> (includes all project branches, mozilla-aurora/beta/releases)

It's a PITA to do #1 and #2 together. Since we're turning off everything on August 27, do we need to bother doing this in the meantime?

> 3) bug#750285 tracks turning off as default on try

This is difficult too. Try configs track mozilla-central, intentionally. Do we want these even as an option after the 27th? If not, I don't think we should bother doing this in the meantime.
(In reply to Ben Hearsum [:bhearsum] from comment #4)
> > 1) Leave android-xul builds and unittests on for mozilla-inbound,
> > mozilla-central. Per bug#771756#c11, this is enough as interim for B2G
> > developers.
> > 2) Disable android-xul builds, unittests and talos on all other branches
> > (includes all project branches, mozilla-aurora/beta/releases)
> 
> It's a PITA to do #1 and #2 together. Since we're turning off everything on
> August 27, do we need to bother doing this in the meantime?

I've hidden Android XUL builds and tests on all trees apart from {mozilla-central,mozilla-inbound,try} given that they cause extra hassle for sheriffs & they'd already be switched off if it were easy to do independently before 27th Aug.
Hmm, I thought that Android XUL is the only platform where we test some of our IPC code.  Has this been discussed with all of the people who want to keep that code working?  AFAIK b2g uses some of that stuff.
Blocks: 784681
We're no longer building or testing android-xul now that bug 774424 has landed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
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.