diff options
| author | Jesse Wilson <jessewilson@google.com> | 2010-02-16 14:30:31 -0800 |
|---|---|---|
| committer | Jesse Wilson <jessewilson@google.com> | 2010-02-16 14:30:31 -0800 |
| commit | 4547cd226e8cdbd8fdaf91cc1fc0c257084d36f1 (patch) | |
| tree | 2cb0851b2de0a89124d1d86263e7d37a27c95cec /dom/src/test/java/org/w3c | |
| parent | 6c231cf6815ba6427035e8e47fc36f9d1139d2fb (diff) | |
| download | libcore-4547cd226e8cdbd8fdaf91cc1fc0c257084d36f1.zip libcore-4547cd226e8cdbd8fdaf91cc1fc0c257084d36f1.tar.gz libcore-4547cd226e8cdbd8fdaf91cc1fc0c257084d36f1.tar.bz2 | |
Reverting our test runner's background building behaviour.
Our continuous build has been failing to complete lately. See:
http://jwilson.mtv.corp.google.com:8080/job/master_passion/274/consoleFull
In addition to this problem the continuous build is compiling many
more tests ahead-of-time than we were originally - previously we
would only have up to 4 tests ready-to-run at any given time. With
this change the ExecutorCompletionService was building and installing
all of the tests eagerly.
I believe the problem might be a mismatch between how the BlockingQueue
and the ExecutorCompletionService select which order to return futures.
By removing the ExecutorCompletionService I remove the opportunity for
such a conflict!
Diffstat (limited to 'dom/src/test/java/org/w3c')
0 files changed, 0 insertions, 0 deletions