Skip to content
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

Test and allow failures against Rails master #421

Merged
merged 2 commits into from
Jan 14, 2013
Merged

Conversation

steveklabnik
Copy link
Member

I think this is how this works, but I'm gonna submit it as a PR so that Travis tries to build it. 😉

If we're testing against ruby-head we should test against Rails master too. Will also help me expose bugs in Rails.

@steveklabnik
Copy link
Member Author

Odd. GitHub doesn't show it as submitted, but: https://travis-ci.org/drapergem/draper/builds/4140218

@haines
Copy link
Contributor

haines commented Jan 14, 2013

I think it's because hasn't started yet, still queued.

@haines
Copy link
Contributor

haines commented Jan 14, 2013

I expect it is going to fail pretty rapidly on master, locally I got uninitialized constant ActiveModel::Validations in our fake AR::Base. I was going to have a look at fixing it but didn't get round to it.

@steveklabnik
Copy link
Member Author

Yeah, I don't plan on making it pass immediately, but it will be good to track progress. Even once it's green, we should leave it in the failures: edge rails is pretty stable, but it'd suck if their build failures affected ours.

@steveklabnik
Copy link
Member Author

... that said, it does look like my Travis syntax is correct.

@haines
Copy link
Contributor

haines commented Jan 14, 2013

Yep indeed! The double-build issue is really annoying now that we're pumping out 12+ jobs per build, it fills up the queue pretty fast! I filed an issue over at travis-ci/travis-ci#855 a couple of days ago but I don't think they've gotten to it yet.

@steveklabnik
Copy link
Member Author

Your suspicion about the build stuff not appearing until it's queued is apparently correct. Neat.

@steveklabnik
Copy link
Member Author

@haines
Copy link
Contributor

haines commented Jan 14, 2013

It looks like it works if you rip the guts out of our fake AR::Base and just do

module ActiveRecord
  class Base
  end
end

Turns out we don't need anything in there at all! (which is nice to know, since unit tests are supposed to be isolated!).

@haines
Copy link
Contributor

haines commented Jan 14, 2013

Try that... poor Travis...

@steveklabnik
Copy link
Member Author

😄

I was like HOW DID YOU GET THAT COMMIT IN THERE and then I remembered I created the branch on the main repo, and not on my own. 😉

Turns out we don't need anything in there at all! (which is nice to know, since unit tests are supposed to be isolated!).

Yeah, a lot of this is ooooold...

@haines
Copy link
Contributor

haines commented Jan 14, 2013

I AM IN YOUR REPO 😈

Looks all good!

haines added a commit that referenced this pull request Jan 14, 2013
Test and allow failures against Rails master
@haines haines merged commit e9b71e3 into master Jan 14, 2013
@steveklabnik steveklabnik deleted the test_rails_master branch January 14, 2013 15:29
@steveklabnik
Copy link
Member Author

🤘

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants