Travis builds not triggered occasionally

[poojanilangekar]

I have noticed this for the past couple of days. Occasionally travis doesn't trigger a build for PRs. Not sure if the issue is because of too many jobs in the queue.

For instance when the master was merged into #1235.
The Travis queue doesn't have a job for it:
https://travis-ci.org/cmu-db/peloton/pull_requests

[tcm-marcel]

I can remember that I also noticed this problems months ago, but I never found a solution for this. It seems that travis just sometimes looses triggers and Github then forever waits for a response.

Using push --force on the same branch may trigger the build again, but that's just a workaround.

[pervazea]

Unclear if this is a Travis bug. I see only trigger history for recent builds (this is too old), otherwise it would be possible to see if Travis got the request and what it did with it.

If the merge is not correct, Travis will record:
GitHub payload is missing a merge commit (mergeable_state: "unknown", merged: false)
and ignore the request.

[tcm-marcel]

Let's wait for the next time this occurs and then check the trigger history. (I didn't know about that)

[tcm-marcel]

@poojanilangekar told me it happened again: #1302 (comment)

@pervazea Can you check the Github trigger history and see if we can see something there?

[pervazea]

The instance I see is: about 19 hours ago addressing pooja's comments GitHub payload is missing a merge commit (mergeable_state: "unknown", merged: false)

…

--- This was followed by another merge commit, which Travis accepted.

________________________________ From: Marcel Kost <notifications@github.com> Sent: Sunday, April 29, 2018 1:44 PM To: cmu-db/peloton Cc: Pervaze Akhtar; Mention Subject: Re: [cmu-db/peloton] Travis builds not triggered occasionally (#1239) @poojanilangekar<https://github.com/poojanilangekar> told me it happened again: #1302 (comment)<#1302 (comment)> @pervazea<https://github.com/pervazea> Can you check the Github trigger history and see if we can see something there? - You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1239 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AhDfwNFSecTeizJfLjFYtvNkAKTy1DQyks5ttfv4gaJpZM4S-8Gm>.

[tcm-marcel]

I see a lot of builds that get not triggered right now, even on my fork.

I guess we can't do anything about that...

[brianonn]

I see this only when the PR merge to the target branch was not successful (i.e. could not be done automatically) due to merge conflicts with the target. With the merge conflicts, travis can't schedule a build