Closed Bug 1088371 Opened 11 years ago Closed 11 years ago

TryChooser needs updating now that 64-bit builds are done on Windows 8

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: n.nethercote, Assigned: sfink)

References

Details

(Keywords: trychooser)

Attachments

(2 files)

Now that 64-bit builds are happening for Windows 8, TryChooser needs several things updated. - The string "win64 (not run by default)" is no longer accurate. - If you choose "win32" but not "win64", do you just get WinXP and Win7 builds? It's unclear. If so, the labels should probably be changed to something like "win32 (XP, 7)" and "win64 (8)". - If you choose "all" platforms, "win64" doesn't get selected. It should. And there are probably other subtleties I'm not aware of.
Keywords: trychooser
I'm a little worried about doing this due to load...but not sure we have much of a choice either.
Attachment #8511094 - Flags: review?(coop)
Attachment #8511094 - Flags: review?(coop) → review+
Attachment #8511094 - Flags: checked-in+
Assignee: nobody → catlee
Are you planning to do the TryChooser UI updates as well in this bug?
I was hoping somebody else would volunteer :) It's been ages since I've touched TryChooser...
(In reply to Nicholas Nethercote [:njn] from comment #0) > Now that 64-bit builds are happening for Windows 8, TryChooser needs several > things updated. Changing this is trivial, though I'm not entirely clear on what the actual configuration is now. But here's the entirety of the patch: - <label><input type="checkbox" name="platform" value="win64" class="nondefault">win64</label> + <label><input type="checkbox" name="platform" value="win64">win64</label> > - The string "win64 (not run by default)" is no longer accurate. That's inserted automatically for the "nondefault" class. > - If you choose "win32" but not "win64", do you just get WinXP and Win7 > builds? It's unclear. If so, the labels should probably be changed to > something like "win32 (XP, 7)" and "win64 (8)". I can never remember how these are arranged, but I don't think this change makes it any more or less complicated. The critical part is that the build platform and the test platform are not the same, and are often different. From looking at the builder names on TH, it looks like 32 bit builds are happening on XP and 64 bit builds are happening on Win7, then the 32 bit builds are run on XP and Win7 and the 64 bit builds are run on Win8. I don't know if the 32 bit builds use a 32-bit or 64-bit compiler, nor whether they are done on a 32- or 64-bit OS. So I don't think this change actually touches the confusing part of this. Few developers have been aware of the difference between build and test platforms, and this doesn't make it any weirder. I think the fix you may want is to better label the "Restrict test(s) to platforms" section, eg make it say XP (32-bit) Win7 (32-bit) Win8 (64-bit) assuming, that is, that the above reflects reality. I have no idea whether it does. > - If you choose "all" platforms, "win64" doesn't get selected. It should. That's automatic if you remove the "nondefault" class. (I knew all this crazy logic would come in handy someday.) > And there are probably other subtleties I'm not aware of. Yeah, same here. :(
Attachment #8513124 - Flags: review?(emorley)
Assignee: catlee → sphink
Status: NEW → ASSIGNED
Attachment #8513124 - Flags: review?(emorley) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: