-
Notifications
You must be signed in to change notification settings - Fork 300
Test to see how Travis is working. #435
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
Conversation
@n2ygk It does look like a recent repo config change affected Travis. This test branch is not running either. |
I'm gonna add a review and see if it unblocks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's see if this approval unblocks Travis
Yep, I saw it in my email just now. |
I'm clicking around the travis stuff some. It showed as not an active integration so I activated it. |
I switched it to run under my profile because it seems to have cleared out @gaker's... Still messing with it. |
That seems to have fixed it. #430 is building now. Please poke this one with a new commit to see if it also works. |
Yep, it's running. |
Ok, this branch did its job and proved that Travis is back so I'm closing it. |
Fixes #
Description of the Change
This is to see if Travis is still triggered on new PRs.
Checklist
CHANGELOG.md
AUTHORS