From 1729b26500506530733753d44f9ce2a2597e0e33 Mon Sep 17 00:00:00 2001 From: Adriaan Moors Date: Tue, 17 Jul 2012 10:02:55 +0200 Subject: move test files that fail spuriously to pending I have this sneaky suspicion that part of these spurious failures are caused by the recent partest optimizations. @axel22 already checked that compiler instances are not shared between test runs. However, except for the benchmark test, they all have a distinct race condition in symbol loading/type checking feel to them. Since, in the end, the tests and/or their corresponding fixes are as likely a culprit as the test framework, moving them out of the way until their owners can get them back in line and they stop throwing primate wenches into our build. We should bring them back as soon as possible, though. --- test/pending/run/t3897.check | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 test/pending/run/t3897.check (limited to 'test/pending/run/t3897.check') diff --git a/test/pending/run/t3897.check b/test/pending/run/t3897.check new file mode 100644 index 0000000000..244b83716f --- /dev/null +++ b/test/pending/run/t3897.check @@ -0,0 +1,8 @@ +(One$$messages,scala.collection.mutable.MutableList) +(One$$messages,scala.collection.mutable.MutableList) +(messages,scala.collection.mutable.MutableList) +(messages,scala.collection.mutable.MutableList) +(One$$messages,scala.collection.mutable.MutableList) +(One$$messages,scala.collection.mutable.MutableList) +(messages,scala.collection.mutable.MutableList) +(messages,scala.collection.mutable.MutableList) -- cgit v1.2.3