[Broken] cucumber/cucumber-rails#101 (master - c79f1b1)

4 views
Skip to first unread message

Travis CI

unread,
Apr 2, 2013, 6:23:23 PM4/2/13
to cukes...@googlegroups.com

The build was broken.

Repository cucumber/cucumber-rails
Build #101 https://travis-ci.org/cucumber/cucumber-rails/builds/5998558
Changeset https://github.com/cucumber/cucumber-rails/compare/97f81e55464e...c79f1b1a4791
 
Commit c79f1b1 (master)
Message Update LICENSE

Added 2012,2013
Author Kosmas Chatzimichalis
Duration 27 minutes and 1 second
You can configure recipients for build notifications in your configuration file. Further documentation about Travis CI can be found here. For help please join our IRC channel irc.freenode.net#travis.

We need your help!

Travis CI has run 406,714 tests for 5,442 OSS projects to date, including Ruby, Rails, Rubinius, Rubygems, Bundler, Node.js, Leiningen, Symfony ...

If you use any of these then you benefit from Travis CI.

Please donate so we can make Travis CI even better!

See all of our sponsors →

aslak hellesoy

unread,
Apr 2, 2013, 6:28:48 PM4/2/13
to Cucumber Developers


--
You received this message because you are subscribed to the Google Groups "Cukes Devs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes-devs+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Kosmas Chatzimichalis

unread,
Apr 3, 2013, 8:53:09 AM4/3/13
to cukes...@googlegroups.com
Sorry Aslak.

Yes, it was not a build fix but while looking at the code I  updated this one as well.

Just trying to fix the build by changing some files here and there.
Tried to remove the rails_4_0 from travis and then tried to other changes to make the build pass again but no luck so far.

Would it be better to try and revert to a working build?

Strange thing is that before pushing the merged master all the local tests were passing fine and that's why I've pushed it to github.
Must be difference between travis and local builds which I cannot find at the moment.

I believe it's some dependency somewhere as the failed tests are trying to install rails4 in the rails 3 gemfile.

Any advice is welcome.

Steve Tooke

unread,
Apr 3, 2013, 9:09:29 AM4/3/13
to cukes...@googlegroups.com
On Wednesday, 3 April 2013 at 13:53, Kosmas Chatzimichalis wrote:
Any advice is welcome.
Not sure if this is relevant or not, but I saw this and this thread reminded me.


Steve

aslak hellesoy

unread,
Apr 3, 2013, 9:13:05 AM4/3/13
to Cucumber Developers
On Wed, Apr 3, 2013 at 1:53 PM, Kosmas Chatzimichalis <kos...@gmail.com> wrote:
Sorry Aslak.

Yes, it was not a build fix but while looking at the code I  updated this one as well.

Just trying to fix the build by changing some files here and there.
Tried to remove the rails_4_0 from travis and then tried to other changes to make the build pass again but no luck so far.

Would it be better to try and revert to a working build?


If you don't know exactly how to fix what's broken, then I think that's the best option.

Aslak
Reply all
Reply to author
Forward
0 new messages