-
Notifications
You must be signed in to change notification settings - Fork 526
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
Conversation
Odd. GitHub doesn't show it as submitted, but: https://travis-ci.org/drapergem/draper/builds/4140218 |
I think it's because hasn't started yet, still queued. |
I expect it is going to fail pretty rapidly on master, locally I got |
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. |
... that said, it does look like my Travis syntax is correct. |
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. |
Your suspicion about the build stuff not appearing until it's queued is apparently correct. Neat. |
You are correct: https://travis-ci.org/drapergem/draper/jobs/4140234/#L89 |
It looks like it works if you rip the guts out of our fake 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!). |
Try that... poor Travis... |
😄 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. 😉
Yeah, a lot of this is ooooold... |
I AM IN YOUR REPO 😈 Looks all good! |
Test and allow failures against Rails master
🤘 |
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.