-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis build failing #4
Comments
It was not intentional to have issues disabled, you did well ! |
Just to update you on where this is at, as I saw you trying to fix the Travis build. Basically Travis are now using OpenVZ on their machines, which ironically is a type of container and therefore conflicts with LXC :( They kindly gave me SSH to a clone of their new box and I had a good look around and there really doesn't seem to be any way to work around it. So I've been researching other CI services and I'm very hopeful for drone.io, see https://drone.io/github.com/openruko/vagrant-openruko I've almost got builds working for a branch of slotbox. I'm also talking to someone at http://beta.wercker.com/ to get beta acess, so hopefully we'll get something working :) |
I pushed two commits, hoping it would fix travis : It fix the node install on travis but not the lxc problem. You seems to have a better idea than me how to get it right with drone or wercker. You can revert my commits if it doesn't help. |
Okay, I'll see what I can do. |
The current Travis build is failing https://travis-ci.org/openruko/vagrant-openruko
Just to let you know I'm aware and will try to get to it working soon. It's errorring when LXC starts for the first time after install.
BTW I've re-enabled Issues for this repo, were they intentionally disabled?
The text was updated successfully, but these errors were encountered: