Build fails on Travis, but not locally

[shoes]

Build fails on Travis, but not locally

[mpapis]

this might be useful http://about.travis-ci.org/docs/user/gui-and-headless-browsers/

[pjfitzgibbons]

We need to figure out how to use a headless display in travis.

SWT will fail if the window methods can't connect to a display device

Peter Fitzgibbons
[phone]
Email: [email protected]
IM GTalk: peter.fitzgibbons
IM AOL: [email protected]

On Fri, May 25, 2012 at 3:19 PM, Eric Watson <
[email protected]

wrote:

There are 24 failures, all with the same error. Here's an example:

Failures:

1) SwtShoes::App Shoes::App shell receives open
Failure/Error: subject { Shoes::App.new }
NativeException:
 org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
# org.eclipse.swt.SWT:-1:in `error'
# org.eclipse.swt.widgets.Display:-1:in `createDisplay'
# org.eclipse.swt.widgets.Display:-1:in `create'
# org.eclipse.swt.graphics.Device:-1:in `<init>'
# org.eclipse.swt.widgets.Display:-1:in `<init>'
# org.eclipse.swt.widgets.Display:-1:in `<init>'
# sun/reflect/NativeConstructorAccessorImpl.java:-2:in `newInstance0'
# sun/reflect/NativeConstructorAccessorImpl.java:57:in `newInstance'
# sun/reflect/DelegatingConstructorAccessorImpl.java:45:in `newInstance'
# java/lang/reflect/Constructor.java:532:in `newInstance'
# org/jruby/javasupport/JavaConstructor.java:259:in `newInstanceDirect'
# ./lib/swt_shoes/app.rb:13:in `gui_init'
# ./lib/shoes/app.rb:39:in `initialize'
# ./spec/swt_shoes/app_spec.rb:15:in `(root)'
# org/jruby/RubyBasicObject.java:1730:in `instance_eval'
# ./spec/swt_shoes/app_spec.rb:20:in `(root)'
# org/jruby/RubyBasicObject.java:1730:in `instance_eval'
# org/jruby/RubyArray.java:2331:in `collect'
# org/jruby/RubyArray.java:2339:in `collect'
# org/jruby/RubyArray.java:2331:in `collect'
# org/jruby/RubyArray.java:2339:in `collect'
# org/jruby/RubyArray.java:2331:in `collect'
# org/jruby/RubyArray.java:2339:in `collect'
# org/jruby/RubyArray.java:2331:in `collect'
# org/jruby/RubyArray.java:2339:in `collect'

I think this might have to do with the TravisCI build VM not having
DISPLAY. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=119156#c1

---

Reply to this email directly or view it on GitHub:
#14

[wasnotrice]

Fixed by cd041ba