|
|
|
[
Permlink
| « Hide
]
Michael Sica - 30/Apr/08 02:08 PM
I forgot to mention that this is a Jruby project.
Yuck, that's one heck of a command line. It looks to me like it broken trying to build up the command line, it's trying to execute jruby.bat by doing:
C:/Program Files/Aptana/Aptana Studio/plugins/org.jruby_1.1.0.5965_RC2p1/bin/C:/Program Files/Aptana/Aptana Studio/plugins/org.jruby_1.1.0.5965_RC2p1/bin/jruby.bat Obviously that's not right. I'm not sure why it's appending a full file path to jruby.bat after the bin directory again. I'll take a look and see if I can dig anything up for why it might do that. Thanks Chris. Not having this working is really ruining my workflow.
Thanks again! Can you check your logs to see the actual command line we tried to execute? The command lien above might have been created by the rake process rather than the IDE...
Help > Aptana Troubleshooting > View Aptana Log File. You should see a line that begins with "Starting: " that then shows the exact command lien we're executing under the hood. The IDE hangs, and becomes completely unresponsive. I've left it sitting there for 10-15 minutes, and then finally kill it through the Windows Task Manager. It doesn't look like it's getting past the db:test:prepare (see log below). But note that it db:test:prepare will work fine when I run it in isolation through the 'Rake Tasks' view or when I run db:functionals through the 'Rake Tasks' view.
— !ENTRY org.radrails.rails.core 1 0 2008-05-05 13:21:38.923 !ENTRY org.rubypeople.rdt.launching 4 4 2008-05-05 13:36:27.805 !ENTRY org.eclipse.ui 4 4 2008-05-05 13:36:30.714 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.379 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.389 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.399 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.399 !ENTRY com.aptana.radrails.sqlite3.win32 1 -1 2008-05-05 13:36:32.399 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:32.961 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:32.961 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:32.961 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:36.160 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:36.160 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:36.160 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:36.170 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:36.170 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-05 13:36:36.261 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-05 13:36:36.261 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-05 13:36:36.271 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.294 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.294 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.294 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.294 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.304 !ENTRY org.eclipse.core.resources 4 372 2008-05-05 13:36:37.304 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-05 13:36:51.116 Many developers at my company have been experiencing this too on an MRI based rails project and on both Windows and Linux.
In linux, the command line I have to kill (from ps) is: /usr/local/bin/ruby -e STDOUT.sync=true -e STDERR.sync=true -e load(ARGV.shift) /usr/local/bin/rake db:test:prepare And if it helps, the Aptana log from my last run is: !SESSION 2008-05-06 09:36:56.640 ----------------------------------------------- !ENTRY org.eclipse.ui 2 0 2008-05-06 09:37:00.809 !ENTRY org.eclipse.ui 4 4 2008-05-06 09:37:04.142 !ENTRY org.eclipse.ui.workbench 2 0 2008-05-06 09:37:10.896 !ENTRY org.eclipse.jface 2 0 2008-05-06 09:37:10.917 !ENTRY org.eclipse.osgi 2 1 2008-05-06 09:37:11.370 !ENTRY org.rubypeople.rdt.debug.ui 4 4 2008-05-06 09:37:11.371 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-06 09:37:12.451 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-06 09:37:12.472 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-06 09:37:12.537 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:13.777 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-06 09:37:13.938 !ENTRY org.rubypeople.rdt.launching 4 4 2008-05-06 09:37:14.183 !ENTRY org.eclipse.debug.core 4 120 2008-05-06 09:37:14.460 !ENTRY org.eclipse.debug.core 4 120 2008-05-06 09:37:14.461 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.207 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.208 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.209 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.210 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.210 !ENTRY org.eclipse.core.resources 4 372 2008-05-06 09:37:19.211 !ENTRY org.radrails.rails.core 1 0 2008-05-06 09:37:23.985 !ENTRY org.rubypeople.rdt.launching 1 -1 2008-05-06 09:37:46.722 Eric: Hmm, that's weird. The logs indicate that the rake db:test:prepare should have finished (we wait for it before we try to start up the test script), yet you say the command stuck in ps is the db:test:prepare.
If you run that exact rake command on the command line (in the project root as the working directory) does it work and finish properly? Are there any errors shown inside the IDE when this whole process fails? (is it failing to connect to the test runner on the port)? Chris, yes runing the same command on the command line succeeds as you would expect.
There are no additional errors shown. All of Eclipse becomes unresponsive (typical UI thread blocked response) untill I kill the rake task mentioned above. However based on your question I did check and when (apparently) hung, /usr/local/bin/ruby -I /home/estewart/apps/eclipse/plugins/org.rubypeople.rdt.launching_1.0.1.200803281641NGT/ruby/flush -rrdt_stream_sync.rb – /home/estewart/workspace/.metadata/.plugins/org.rubypeople.rdt.testunit/RemoteTestRunner.rb /home/estewart/workspace/.metadata/.plugins/org.radrails.rails.core/run_tests.rb 4000 false For our project, db:test:prepare usually completes in under 30 seconds, but trying to wait out Testruner (whith GUI hung and not repainting) for much greater lengths of time does not change anything. Let me know if there is anything else I can try or tell you. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||