It makes a good addition to trybot flags (it shouldn't be the default.)
Rationale:
when testing compiler changes, we probably want to get as much
information as possible, esp. when the author doesn't have access
to that hardware.
Knowing that a particular change breaks /test/some.go is generally
more valuable than, say, knowing it breaks image/draw tests.
/cc @bradfitz
It makes a good addition to trybot flags (it shouldn't be the default.)
Rationale:
when testing compiler changes, we probably want to get as much
information as possible, esp. when the author doesn't have access
to that hardware.
Knowing that a particular change breaks /test/some.go is generally
more valuable than, say, knowing it breaks image/draw tests.
/cc @bradfitz