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

Investigating Travis DO NOT MERGE [skip appveyor] #4197

Conversation

nicoddemus
Copy link
Member

Investigating #4195 (comment)

@nicoddemus
Copy link
Member Author

nicoddemus commented Oct 19, 2018

Hmmm this push started two builds:

image

@nicoddemus nicoddemus force-pushed the investigate-travis-double-builds-1 branch from 5b3ed28 to 8fce67d Compare October 19, 2018 01:29
@nicoddemus
Copy link
Member Author

Hmmm git push --force:

image

@nicoddemus nicoddemus force-pushed the investigate-travis-double-builds-1 branch from 8fce67d to d4bc568 Compare October 19, 2018 01:31
@nicoddemus
Copy link
Member Author

I noticed that we have both GitHub service and GitHub app enabled for pytest repository, disabled the GitHub service for Travis and made another push --force:

image

image

@nicoddemus
Copy link
Member Author

OK, it seems the cause was to have both services enabled at the same time...

Let me reactivate the GitHub service and push again to confirm. It should again open two PRs.

@nicoddemus nicoddemus force-pushed the investigate-travis-double-builds-1 branch from d4bc568 to b8e6667 Compare October 19, 2018 01:35
@nicoddemus
Copy link
Member Author

Yep, again two new builds for the same commit:

image

@nicoddemus
Copy link
Member Author

OK, it seems the problem is that we had Travis enabled as a GitHub App and GitHub Service at the same time.

I'm disabling the GitHub service given that it has been deprecated for some time now. 👍

Hopefully this will fix Travis for good now.

@nicoddemus nicoddemus force-pushed the investigate-travis-double-builds-1 branch from b8e6667 to 4d68f87 Compare October 19, 2018 01:38
@nicoddemus
Copy link
Member Author

Final confirmation:

image

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.

1 participant