Closed Bug 950206 Opened 11 years ago Closed 11 years ago

Enable 32-bit Windows builds on Date, test those builds on tst-w64-ec2-XXXX

Categories

(Release Engineering :: General, defect)

x86
Windows 8
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhopkins, Assigned: jhopkins)

References

Details

Attachments

(2 files, 1 obsolete file)

Enable 32-bit Date branch builds and test them on the Windows 64-bit test machines (tst-w64-ec2-XXXX) to separate out things that are purely 64-bit test failures vs. things that are gpu/rendering/aws dependent.
TODO: make sure testing of 32-bit builds is happening on the win64_vm build machines.
Armen: I'm not sure it is possible to do this cleanly with our current config setup, however I have limited understanding of the test configs. Can we work together on this, please?
Flags: needinfo?(armenzg)
Sure. Can we meet tomorrow morning?
Flags: needinfo?(armenzg)
Thanks, Armen. I actually just had a call with Aki and he helped me understand the right way to go about this: Rather than testing 32-bit builds on win32 and win64 test slaves, only test 32-bit builds on win64 test slaves. We can do that fairly easily by modifying the slaves list in the test config for just the 'date' branch. If there is a need to test 32-bit builds on win32 test slaves, that can still be accomplished via the 'try' branch rather than try and support a more complex 'date' branch configuration (which is what I had been trying to do but it's a lot more work).
Attachment #8358591 - Flags: review?(aki)
Comment on attachment 8358591 [details] [diff] [review] [buildbot-configs] trigger win64 unit tests for 'date' branch win32 builds I think that will do the trick.
Attachment #8358591 - Flags: review?(aki) → review+
Comment on attachment 8358591 [details] [diff] [review] [buildbot-configs] trigger win64 unit tests for 'date' branch win32 builds https://hg.mozilla.org/build/buildbot-configs/rev/5fb25f34b444
Attachment #8358591 - Flags: checked-in+
in production
Here's a recent push after this went live: https://tbpl.mozilla.org/?tree=Date&rev=aec43837db9f Looks like it's not quite correct... the only 32-bit tests that got done/scheduled seem to be talos (which we explicitly don't need in this instance), and they were done on the wrong machines (they went on the regular 32-bit machines, not the VMs).
There's two sets of pending tests on tbpl's Win64 line because it doesn't know from 32-bit-build-on-64-bit-slave. And since we haven't had a running tst-w64-ec2 slave since November 13th, those'll be pending until someone recreates enough slaves to run those plus however much Try backlog there is since the last time I killed all the pending jobs on Try.
Depends on: 925204
Ah, I just noticed the duplicated pending tests. Ok, that's fine if it's a display issue. The try stuff is a concern. For now those VMs should be isolated to just testing on the date branch. (And try shouldn't be issuing 64-bit windows test runs, since we should have nothing to handle them!)
Do we need to remove win64 from trychooser as well?
Attachment #8360451 - Flags: review?(catlee)
Comment on attachment 8360451 [details] [diff] [review] [buildbot-configs] disable Win64 testing on Try Review of attachment 8360451 [details] [diff] [review]: ----------------------------------------------------------------- people way still want win64 builds?
Attachment #8360451 - Flags: review?(catlee) → review+
Attachment #8360451 - Flags: checked-in+
Depends on: 960594
Depends on: 960608
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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: