code review 111400043: build: be verbose when running tests on Plan 9

build: be verbose when running tests on Plan 9

This is a temporary change to see how far the
builder gets when it times out.

[ality, 2014-07-20 05:55:32]

Hello 0intro@gmail.com, aram@mgk.ro (cc: golang-codereviews@googlegroups.com,
mischief@offblast.org),

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

[ality, 2014-07-20 06:22:04]

I think the builder is timing out because we run
out of memory and one of the runtime procs gets
killed instantly with no chance to notify the other
procs. This may be causing run.go to wait around
for the others.

We'll see.

Cheers,
  Anthony

[aram, 2014-07-20 09:24:28]

LGTM

I'm not sure this will tell us anything because as far as I could see, hangs are
pretty random, but as an experiment we can try it.

Another reasons why procs might be killed is because they might use SSE2 in note
handlers. That is solvable, I'll write about it.

[0intro, 2014-07-20 09:31:42]

LGTM

I'm not sure we will learn anything more
useful than what is described in issue 7462.

But OK, let's try.

I'm also pretty sure that the builder doesn't
run out of memory, but there might be other
reasons causing processes to be killed.

[aram, 2014-07-20 10:15:09]

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

build: be verbose when running tests on Plan 9

This is a temporary change to see how far the
builder gets when it times out.

LGTM=aram, 0intro
R=0intro, aram
CC=golang-codereviews, mischief
https://codereview.appspot.com/111400043

Committer: Aram Hăvărneanu <aram@mgk.ro>