You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The slowbots feature (e.g. setting "TRY=") is extremely helpful for developers who want to get expanded test coverage for their CLs (particularly with the more obscure GOOS/GOARCH combos). This was a big help for the team when rewriting the linker this last year.
Another feature that would make developers lives easier would be to allow the setting of GOEXPERIMENT=... in a Gerrit reply or comment, and then have that setting picked up and used when doing the builder runs.
Two cases that come to mind immediately are field tracking, e.g. GOEXPERIMENT=fieldtrack, which seems to break on a semi-regular basis due to lack of regular testing, and GOEXPERIMENT=regabi. At the moment developers working on the register ABI project can do local testing by setting GOEXPERIMENT before running make.bash or all.bash, but there isn't an easy way for them to do testing over a wider set of builders.
The text was updated successfully, but these errors were encountered:
One thing I should add: with some experiments it makes sense to have just a single builder (ex: field tracking, static lock ranking), but there could easily be experiments that we want to test on a wider set of architecture/OS combinations.
If there are configurations for which we want to run the standard tests to prevent regressions, those configurations should have builders even if we use some other mechanism instead of GOEXPERIMENT. (The Beyoncé Rule applies here.)