Re: [scalatest-users] Exit code 255

[Bill Venners]

Hi Richard,

I don't have an explanation. I have seen Scala (not Akka) actors die-ing on non-main-test threads in both IntelliJ and sbt, and it has never taken them out. Can't imagine how it could kill those processes happen. When you are executing ScalaTest in the REPL you are only executing ScalaTest through a suite's run method. Can you post back the exact command you are using to run through the REPL?

Also if you could try running from the command line through ScalaTest's Runner and let me know the result, that might be a clue. That one is a pain because you have to figure out all the dependencies that sbt is using to specify the classpath. Might be a pain to figure out, but if you can do it, that could help isolate the problem.

Bill

On Mon, Aug 20, 2012 at 5:17 AM, Richard Wise <richar...@googlemail.com> wrote:

I have a complex end-to-end test that when executed via SBT causes SBT to silently exit, when executed inside IntelliJ aborts with "Process finished with exit code 255", but when executed in the Repl actually runs. In both SBT and IntelliJ the process is killed without displaying any error messages or diagnostic help.

The actual test invokes Akka actors and has an uncaught error on one of the Akka threads, but it is concerning that this is able to take out ScalaTest inside SBT and IntelliJ.

Can anyone explain the difference between ScalaTest execution inside SBT and IntelliJ, as opposed to via the Repl, and how running a test inside SBT is able to completely kill the process?

Cheers.

--
You received this message because you are subscribed to the Google
Groups "scalatest-users" group.
To post to this group, send email to scalate...@googlegroups.com
To unsubscribe from this group, send email to
scalatest-use...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/scalatest-users?hl=en
ScalaTest itself, and documentation, is available here:
http://www.artima.com/scalatest

--
Bill Venners
Artima, Inc.
http://www.artima.com

[Richard Wise]

Hi Bill,
To summarise the behaviour of the different ways of running ScalaTest (from http://www.scalatest.org/user_guide/running_your_tests) that I have tried:

• ScalaTest Runner - process terminates silently,
• Scala intepreter (REPL using (new Test).execute syntax) - test executes,
• SBT ScalaTestFramework - SBT terminates silently,
• IntelliJ JUnitRunner - process teminates with exit code 255

Hope this helps clarify the problem.

Cheers.

Rich

[Bill Venners]

Hi Richard,

When you say "terminates silently" you mean there is no output at all? Are you using the stdout reporter for example, and it is printing nothing?

Bill

[Richard Wise]

Hi Bill,

The process terminates without any output on stdout or stderr - running in a console drops back to console without any messages. I am not familiar with stdout reporter - is this a ScalaTest feature?

Cheers,

Richard

[Bill Venners]

Hi Richard,

Yes, if you pass -o to Runner it will print results to the standard output. How are you running your tests when you run with the Runner? Also, what version of ScalaTest are you using?

Bill