Travis CI

26 views
Skip to first unread message

Tim Felgentreff

unread,
Jan 13, 2013, 10:57:47 AM1/13/13
to maglev-d...@googlegroups.com
Hi,

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.

Cheers,
-Tim

Steven R. Baker

unread,
Jan 13, 2013, 11:16:16 AM1/13/13
to maglev-d...@googlegroups.com
> 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 :)

All I did was pay for a service we use. I'm really glad to see that it'll be working on MagLev soon. We are launching the first app this month (I hope!), and Travis is an important part of our workflow.

-Steven

Tim Felgentreff

unread,
Jan 14, 2013, 1:38:19 PM1/14/13
to Tim Felgentreff, maglev-d...@googlegroups.com
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 Felgentreff
Sent: 13/01/2013 16:57
To: maglev-d...@googlegroups.com
Subject: [maglev-discussion] Travis CI

Hi,


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.

Cheers,
-Tim

--
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.

Jesse Cooke

unread,
Jan 14, 2013, 2:53:10 PM1/14/13
to maglev-d...@googlegroups.com
Check out section 4: Implementations, specifically the compliance guards. Maybe that'll help for now?


--------------------------------------------
Jesse Cooke :: N-tier Engineer
jc00ke.com / @jc00ke

Tim Felgentreff

unread,
Jan 15, 2013, 9:38:53 AM1/15/13
to maglev-d...@googlegroups.com
I've changed our code so we raise a TypeError (as MRI would when passed a nil argument) and the spec is tagged. I would've expected it to be ignored, now, but it still shows up as an error on travis (https://travis-ci.org/MagLev/maglev/jobs/4165419). On my local machine, even if I change the spec to manually raise an error, the tag is respected and the error ignored.
 
Any idea why the tag might be ignored on travis?

Tim Felgentreff

unread,
Jan 15, 2013, 10:01:21 AM1/15/13
to maglev-d...@googlegroups.com
Argh, my bad, I've misread ... core/file/stat/ftype_spec.rb kept failing, and I kept looking at core/file/ftype_spec.rb. all pass now.
Reply all
Reply to author
Forward
0 new messages