diff options
author | Adriaan Moors <adriaan.moors@epfl.ch> | 2012-07-17 10:02:55 +0200 |
---|---|---|
committer | Adriaan Moors <adriaan.moors@epfl.ch> | 2012-07-17 17:26:27 +0200 |
commit | 1729b26500506530733753d44f9ce2a2597e0e33 (patch) | |
tree | fb21521e8f5d9e4dbf1cc9bcdadc4485492586e3 /test/files/pos/t294/Test_1.scala | |
parent | 022eed3245db21f5faf06ae6472e585ead137f82 (diff) | |
download | scala-1729b26500506530733753d44f9ce2a2597e0e33.tar.gz scala-1729b26500506530733753d44f9ce2a2597e0e33.tar.bz2 scala-1729b26500506530733753d44f9ce2a2597e0e33.zip |
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.
Diffstat (limited to 'test/files/pos/t294/Test_1.scala')
-rw-r--r-- | test/files/pos/t294/Test_1.scala | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/test/files/pos/t294/Test_1.scala b/test/files/pos/t294/Test_1.scala deleted file mode 100644 index ff1f34b10e..0000000000 --- a/test/files/pos/t294/Test_1.scala +++ /dev/null @@ -1,7 +0,0 @@ -// also test pickling of java annotations; Test_2.scala will -// read this class file -@Ann(nested = Array(new Ann2(10))) class Test { - @Ann2(100) var ctx: Object = _ - @Ann(nested = Array()) def foo = 10 - @Ann(nested = Array(new Ann2(10), new Ann2(23))) val bam = -3 -} |