- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
test failure on neg/t3222.scala
Sun, 2010-05-23, 20:24
So I've been seeing test neg/t3222.scala failing. I'm not sure when it
began, and it doesn't seem to be happening to the robots. Has anyone
else seen this? The failure is that only three errors are printed
instead of the four in the checkfile.
As a fun extra tidbit it only fails unoptimized; ant test-opt passes it
through fine. Maybe that's why the bots are cool with it.
I notice the output in the checkfile actually reports the errors out of
order (line 4 before line 3) so it's a generous definition of "expected"
output and that oddity may be relevant.
The test source is:
@throws(classOf[B])
class ExceptionTest {
@throws(classOf[C])
def foo(@throws(classOf[D]) x: Int) {}
@throws(classOf[E])
type t = String
}
My output is:
t3222.scala:1: error: not found: type B
@throws(classOf[B])
^
t3222.scala:4: error: not found: type D
def foo(@throws(classOf[D]) x: Int) {}
^
t3222.scala:6: error: not found: type E
@throws(classOf[E])
^
three errors found
Expected output is:
t3222.scala:1: error: not found: type B
@throws(classOf[B])
^
t3222.scala:4: error: not found: type D
def foo(@throws(classOf[D]) x: Int) {}
^
t3222.scala:3: error: not found: type C
@throws(classOf[C])
^
t3222.scala:6: error: not found: type E
@throws(classOf[E])
^
four errors found