Treeherder labeling for Windows/Linux 32-bit builds should be explicit about 32-bit-ness (and maybe drop `x64` from the x64 builds)
Categories
(Tree Management :: Treeherder: Frontend, defect)
Tracking
(Not tracked)
People
(Reporter: Gijs, Unassigned)
Details
People may assume that build/test runs that simply say "Linux opt" or "Windows 2012 Shippable" are "the right ones" and the ones with x64/Aarch64 are special / not the ones they want.
This is unfortunate because 32-bit builds on x64 infra (which is what 99.99% of folks will then run it on in 2024) are gonna be pretty slow and/or run out of memory sooner.
It would be nice if we could fix the labeling to make this more obvious. Perhaps we should also drop the x64 suffix from the x64 builds. All of this would also help us more quickly spot out-of-memory type issues in tests as being correlated with the 32-bit-ness of the build (which has definitely bit me in the past in e.g. bug 1731059 and its many friends).
|
||
Comment 1•2 years ago
|
||
This would be a good opportunity to adapt the same conventions we're already using for Linux & Mac (i.e. dropping the highly-misleading "2012" version number and just going with Platform + Arch for builds).
Description
•