CreateProcess error=206, The filename or extension is too long when trying to run ScalaTest in ScalaIDE on Windows 7 64bit

4,237 views
Skip to first unread message

Tong Chen

unread,
Nov 14, 2013, 6:17:01 PM11/14/13
to scalate...@googlegroups.com
I got the following error when trying to run ScalaTest from Eclipse using "Runas -> ScalaTest - File" from context menu

Exception occurred executing command line.

Cannot run program ""[PATH to javaw.exe]"" (in directory "[path to the project]"): CreateProcess error=206, The filename or extension is too long

Launching the very same test using "Runas -> Scala Junit Test" is fine.

Here are the details of my envionrment:

Eclipse 20130919-0819

Scala IDE for Eclipse 3.0.2.v-2_10-201310181157-0880865

Sorry if the above information not enough for investigation as I am not quite sure how to dig a bit deeper to get more information such as logs. 

I guess the question I want to ask are 

1. What are the differences between running scalatest using "ScalaTest - File" and "Scala Junit Test"

2. How can I see the command line it (ScalaTest - File) uses to run the tests?


Many Thanks,

Tong

Tong Chen

unread,
Nov 15, 2013, 7:46:23 AM11/15/13
to scalate...@googlegroups.com
Some additional info.
For the same project and same test cases in the same IDE, I can run them perfectly on Mac. But failed to run on both parallel VM windows 7 64bit and native windows 7 64bit.

Chee Seng Chua

unread,
Nov 15, 2013, 9:02:48 AM11/15/13
to scalate...@googlegroups.com
Hi Tong, 

Sorry for replying late, was busy getting the ScalaTest plugin to work for scala-ide 4.0.0-M1 milestone today.  The problem sounds like a windows path limitation problem.  A quick google result seems that ScalaTest plugin is not alone: 


They suggested workaround like -cp to a generated classpath, which I'll try to investigate.  For your info, here's the source code responsible for launching: 


It is interesting to know that "Scala Junit Test" one works though, I can try to study the related source code (probably early next week) to see if there's a solution, and since I don't have access to a window system it will be great if you can help to verify if there's a solution later. :)

Cheers, 
Chee Seng



On Fri, Nov 15, 2013 at 8:46 PM, Tong Chen <chent...@gmail.com> wrote:
Some additional info.
For the same project and same test cases in the same IDE, I can run them perfectly on Mac. But failed to run on both parallel VM windows 7 64bit and native windows 7 64bit.

--
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
---
You received this message because you are subscribed to the Google Groups "scalatest-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalatest-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Tong Chen

unread,
Nov 16, 2013, 11:08:11 AM11/16/13
to scalate...@googlegroups.com
Thanks Chee Seng, this community forum for developer support is certainly one of the most responsive ones I have ever used. I am really impressed that many actual committers are helping us here.

Chee Seng Chua

unread,
Nov 18, 2013, 7:08:23 AM11/18/13
to scalate...@googlegroups.com
Hi Tong, 

I studied the source code of JUnit plugin and the ticket on eclipse itself: 


Though it is already marked as resolved/closed, Jimisola Laursen reported at the end of the list that he still encounter that in the latest kepler sr1 with the same build id that you reported.  I managed to workout a solution and build a new version, but it could take sometime for scala-ide guys to pull it (if they didn't, there's a scheduled task that runs once a day to pull new build), when the update is available later can you try to see if it fix your problem?

Cheers, 
Chee Seng

Tong Chen

unread,
Nov 18, 2013, 10:36:30 AM11/18/13
to scalate...@googlegroups.com
Great, thanks Chee Seng, I will give it a go and update here. 

Best Wishes,
Tong

Tong Chen

unread,
Nov 19, 2013, 5:32:58 AM11/19/13
to scalate...@googlegroups.com
Hi Chee Seng,

Your fix worked. I used the one from http://download.scala-ide.org/sdk/e38/scala210/dev/site/plugins/ and tried on both Selenium and Unit Scala tests. They both working fine. :)
Thanks a lot for the super quick fix.

Best Wishes,
Tong

Chee Seng Chua

unread,
Nov 19, 2013, 6:45:19 AM11/19/13
to scalate...@googlegroups.com
Hi Tong, 

Thanks for verifying the fix!

Cheers, 
Chee Seng

navisa...@gmail.com

unread,
Oct 28, 2015, 11:48:38 AM10/28/15
to scalatest-users
Also try "Long Path Tool". It helped me with Error 1320 in Windows 7. :)

navisa...@gmail.com

unread,
Oct 28, 2015, 11:48:40 AM10/28/15
to scalatest-users
 
Also try "Long Path Tool". It helped me with Error 206 in Windows 7. :)

Roksolana

unread,
Jun 4, 2016, 12:27:41 PM6/4/16
to scalatest-users
Long Path Tool” is very helpful for this error !
You can use to solve this problem
thanks

palas...@gmail.com

unread,
Aug 16, 2016, 6:36:23 AM8/16/16
to scalatest-users

palas...@gmail.com

unread,
Aug 16, 2016, 6:36:23 AM8/16/16
to scalatest-users
“Long Path Tool” is very helpful for this error !

palas...@gmail.com

unread,
Aug 16, 2016, 6:36:24 AM8/16/16
to scalatest-users
Reply all
Reply to author
Forward
0 new messages