librelist archives

« back to archive

Running specs on OS X 10.6.8 w/ Java 1.6.0_43-b01-447

Running specs on OS X 10.6.8 w/ Java 1.6.0_43-b01-447

From:
Seth Thomas Rasmussen
Date:
2013-04-03 @ 19:55
Hi all,

I picked up Shoes4 today. Getting the environment setup was smooth. The
specs all pass, but the rake process hangs after printing out the "Coverage
report generated..." statement at the end. At that point I found the SWT
application spawned to be unresponsive.

If I interrupt the terminal process, the SWT process remains in its
unresponsive state.

If I force quit the SWT process, the terminal process explodes like so:

rake aborted!
Command failed with status (143): [jruby --debug --1.9 -Ispec
-J-XstartOnFirs...]

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/file_utils.rb:53:in
`create_shell_runner'
org/jruby/RubyProc.java:249:in `call'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/file_utils.rb:45:in
`sh'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/file_utils_ext.rb:41:in
`sh'
/Users/srasmussen/p/shoes4/Rakefile:19:in `jruby_run'
/Users/srasmussen/p/shoes4/Rakefile:37:in `jruby_rspec'
/Users/srasmussen/p/shoes4/Rakefile:100:in `(root)'
org/jruby/RubyProc.java:249:in `call'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:246:in
`execute'
org/jruby/RubyArray.java:1613:in `each'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:241:in
`execute'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:184:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:177:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:170:in
`invoke'
/Users/srasmussen/p/shoes4/Rakefile:91:in `(root)'
org/jruby/RubyProc.java:249:in `call'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:246:in
`execute'
org/jruby/RubyArray.java:1613:in `each'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:241:in
`execute'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:184:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:177:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:170:in
`invoke'
/Users/srasmussen/p/shoes4/Rakefile:87:in `(root)'
org/jruby/RubyProc.java:249:in `call'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:246:in
`execute'
org/jruby/RubyArray.java:1613:in `each'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:241:in
`execute'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:184:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:177:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:205:in
`invoke_prerequisites'
org/jruby/RubyArray.java:1613:in `each'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:203:in
`invoke_prerequisites'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:183:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:177:in
`invoke_with_call_chain'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/task.rb:170:in
`invoke'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:143:in
`invoke_task'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:101:in
`top_level'
org/jruby/RubyArray.java:1613:in `each'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:101:in
`top_level'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:110:in
`run_with_threads'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:95:in
`top_level'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:73:in
`run'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:160:in
`standard_exception_handling'

/Users/srasmussen/.rvm/gems/jruby-1.7.2@global/gems/rake-10.0.4/lib/rake/application.rb:70:in
`run'
org/jruby/RubyKernel.java:1046:in `load'
org/jruby/RubyKernel.java:1066:in `eval'
/Users/srasmussen/.rvm/gems/jruby-1.7.2@shoes/bin/ruby_noexec_wrapper:14:in
`(root)'
Tasks: TOP => spec:swt:all
(See full trace by running task with --trace)

It's been a while since I had Shoes on, and I'm a newbie regarding
debugging jRuby, so I'm wondering if this speaks to anything more obvious
to the Shoes/jRuby veterans among us. If I knew where to start, I'd be
willing to take a stab at fixing this little hiccup.

Re: [shoes] Running specs on OS X 10.6.8 w/ Java 1.6.0_43-b01-447

From:
Steve Klabnik
Date:
2013-04-03 @ 20:45
Great to see you, Seth!

Re: [shoes] Running specs on OS X 10.6.8 w/ Java 1.6.0_43-b01-447

From:
Eric Watson
Date:
2013-04-03 @ 21:05
On Apr 3, 2013, at 2:55 PM, Seth Thomas Rasmussen <sethrasmussen@gmail.com> wrote:

> Hi all,
> 
> I picked up Shoes4 today. Getting the environment setup was smooth. The 
specs all pass, but the rake process hangs after printing out the 
"Coverage report generated..." statement at the end. At that point I found
the SWT application spawned to be unresponsive. 
> 
> If I interrupt the terminal process, the SWT process remains in its 
unresponsive state.

Hi, Seth.

I think that problem is related to this issue I just submitted on Github: 

https://github.com/shoes/shoes4/issues/226

Try running an app like this:

$ bin/shoes samples/sample1.rb

Do you get the error listed in that issue? I'm on 10.8.2, and I wondered 
if it had to do with my OS version, but I see you're on 10.6.8, so that 
helps narrow it down. I did a cursory google search on the error, and it 
seems to have popped up at one time with Qt, so maybe this is an Swt 
issue.

Eric