1359506 - Re-enable Win64 tests on Try by default

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement, P3)

Description

[Chris Peterson [:cpeterson]]

"Windows 8 x64 opt" Try jobs were disabled in bug 1255533, so we now have no win64 tests running by default on Try. Now that we're rolling out 64-bit Firefox as the default for eligible users (bug 1340936, about 70% of all Firefox users are running Win64 OS), we should re-enable win64 tests on Try.

Re-enabling these Try tests is not a critical priority because we're still running win64 tests on autoland/inbound/central. But it would just be nice to help developers catch problems on win64, what will soon be our most common platform by far, on Try before they land.

Coop says re-enabling win64 tests is blocked on standing up Win10 in Taskcluster (bug 1326419).

Comment 1

[Chris AtLee [:catlee]]

Amy, can you comment on our capacity here?

Comment 2

[Amy Rich [:arr] [:arich]]

Transfering the NI to :randi, the PM of the taskcluster migration project, since she'll have a better idea of dates for the AWS portion. From my understanding, we also either need to be using BBB so that we're testing buildbot jobs, or complete taskcluster windows signing so we can ship taskcluster builds. Between jmaher, catlee, and randi, I suspect the complete picture can be determined.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

right now 64 bit firefox for windows is tested via windows 8, this is 100% on hardware and every day of the week we typically have around a 1000 queue backlog:
https://www.hostedgraphite.com/da5c920d/86a8384e-d9cf-4208-989b-9538a1a53e4b/grafana/dashboard/db/pending?from=now-30d&to=now

this goes down fast, so it isn't so painful.  I suspect we are at capacity or slightly over (maybe 105% load).  If we doubled the volume of tests on win8, I will guarantee trees will close often.  Most likely we would see a 30-60% increase in load on the hardware.

If we could turn off non-e10s tests for win8, that would reduce our load by ~30%, and right there we would be closer to supporting win8 on try by default.  In fact disabling all non-e10s tests would free up some hardware from linux64 and windows7 so we could increase the pool size for windows8.  In the near future we will have tests running in AWS on Windows 10, that future is still pending a few weeks of solid work, probably something more likely in July timeframe based on the rate of fixes for the bugs to date.  The platform needs to be build up to support testing and that is tracked in bug 1326419.

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Joel Maher ( :jmaher) from comment #3)
\> In the near future we will have tests running in AWS on Windows 10, that
> future is still pending a few weeks of solid work, probably something more
> likely in July timeframe based on the rate of fixes for the bugs to date. 
> The platform needs to be build up to support testing and that is tracked in
> bug 1326419.

Thanks, Joel. Enabling 64-bit tests on Try by default is not a critical priority because we still have 64-bit tests elsewhere, so I don't think there is any work your team needs to do for this right now. Please just keep it in mind when you are retiring the win8 hardware and standing up win10 in Taskcluster. I'll check back in with you in June/July.

Comment 5

[Chris Peterson [:cpeterson]]

Re-enabling Win64 tests on Try by default does not block our win64 rollout (meta bug 1340936).

Comment 6

[Aki Sasaki (not active)]

We've moved to taskcluster and ./mach try fuzzy since this bug was filed; win64 is fully supported afaik.