code review 9573043: test: do not run the test that relies on precise GC on ...

test: do not run the test that relies on precise GC on 32-bits
Currently most of the 32-bit builder are broken.
Fixes issue 5516.

[dvyukov, 2013-05-20 06:57:10]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://dvyukov%40google.com@code.google.com/p/go/

[dave_cheney.net, 2013-05-20 07:01:27]

Thank you for this quick fix. 

I'm not sure that precise GC is exactly the cause, several arm builds have
passed after 2c128d417029 was submitted, whereas 100% of the 386 builders have
failed since that commit.

[dvyukov, 2013-05-20 07:08:51]

On 2013/05/20 07:01:27, dfc wrote:
> Thank you for this quick fix. 
> 
> I'm not sure that precise GC is exactly the cause, several arm builds have
> passed after 2c128d417029 was submitted, whereas 100% of the 386 builders have
> failed since that commit.

Frankly, I just do not want to spend time investigating. Even if main cause is
not precise GC right now, it still can be flaky on 32-bits due to precise GC and
completely unrelated changes can break it in future.

[dave_cheney.net, 2013-05-20 07:14:04]

> Frankly, I just do not want to spend time investigating. Even if main cause is
> not precise GC right now, it still can be flaky on 32-bits due to precise GC
and
> completely unrelated changes can break it in future.

That is a fair statement, I believe you are correct. I would like to hear from
Rémy, or Iant before disabling this test.

[iant, 2013-05-20 17:28:05]

LGTM

[dvyukov, 2013-05-20 17:53:38]

*** Submitted as https://code.google.com/p/go/source/detail?r=c0f8999bd970 ***

test: do not run the test that relies on precise GC on 32-bits
Currently most of the 32-bit builder are broken.
Fixes issue 5516.

R=golang-dev, dave, iant
CC=golang-dev
https://codereview.appspot.com/9573043