I've enabled rubyspecs after tagging the failing ones on another machine that has those failures. There's one more failure, in which an error from the VM comes up. I'll have to find out how to tell rubyspec that it mustn't run that spec, and not just that failure is expected. @monty, @peter: do you happen to know how to do it?
From: Tim FelgentreffSent: 13/01/2013 16:57
Subject: [maglev-discussion] Travis CI
I've enabled the github repository to run the vmunit tests on travis-ci, after Konstantin told me that they're in the process of adding 64bits VMs. He also said we should say thanks to Steven Baker for supporting Travis to make MagLev possible on their infrastructure, so thanks Steven :)
I have only enabled vmunit, not rubyspecs for now, because there's some failures on travis that I don't see on my machine, I'll have to investigate.
You received this message because you are subscribed to the Google Groups "MagLev Discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/maglev-discussion/-/D9keF0mqxSsJ
To post to this group, send email to maglev-d...@googlegroups.com
To unsubscribe from this group, send email to maglev-discuss...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/maglev-discussion?hl=en