Closed Bug 1141280 Opened 8 years ago Closed 6 years ago

Add T testing to the trychooser UI

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 941183

People

(Reporter: armenzg, Unassigned)

Details

(Keywords: trychooser)

Ehsan mentioned to me that a lot of code changes require testing on all builds but only test on one platform (since the changes are not platform dependent).

This is what its called T testing and we should help developers choose that option over others.

These days in order to choose T testing we have to:
1) select "both" for types of builds
2) select "all" for all platforms (non-default options are not checked)
3) select one platform under "Restrict tests to platform(s)"

The try message looks like this:
try: -b do -p linux,linux64,linux64-asan,linux64-st-an,linux64-valgrind,linux64-br-haz,linux64-b2g-haz,linux64-mulet,macosx64,macosx64-mulet,win32,win32-mulet,win64,android-api-9,android-api-11,android-x86,emulator,emulator-jb,emulator-kk,emulator-l,linux32_gecko,linux64_gecko,macosx64_gecko,win32_gecko -u none[x64] -t none

http://trychooser.pub.build.mozilla.org
Keywords: trychooser
Since it already *was* added to trychooser (that's what the "restrict tests to platform(s)" UI is for), I presume you mean we should "Implement a sane trychooser string and default to that".

Of course, nobody has done so because there is no sane default: sometimes T testing is a fairly good idea, and sometimes a Linux is a good choice for platform, and other times you're affecting something for which the tests are disabled on Linuxes and a Linux is a terrible choice and still other times you're only going to break tests on one platform and you don't know which one it will be.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 941183
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.