Open Bug 1649795 Opened 5 years ago Updated 5 years ago

Push to PR intermittently not triggering / reflecting on Github

Categories

(Taskcluster :: Operations and Service Requests, task)

Product:
Taskcluster
Component:
Operations and Service Requests
Type:
task

Tracking

(Not tracked)

People

(Reporter: gerard-majax, Unassigned)

Details

Happened at least three times today on this PR: https://github.com/mozilla/DeepSpeech/pull/3103
git commit --amend followed by git push --force, would not trigger a new build visible on Github even after 5-10 minutes.
At the time of the repro (01/07/2020, 10:50 and 17:26 CEST) there was no mention of outage on githubstatus.com

I saw the webhook come in to the tc-github-web pod, with event-id 3aca6100-bb79-11ea-96b5-4c826c850351 at 2020-07-01 09:00:00.912 GMT.

The logging level on the handlers pod is such that it is not logging further information about handling of pull requests. Can we shift that level down to DEBUG for tc-github in community-tc?

Flags: needinfo?(bpitts)
Assignee: nobody → dustin

I'm going to move all log level config to https://github.com/mozilla-services/cloudops-infra/pull/2272 for visibility

This is deployed.

Flags: needinfo?(bpitts)

Great! Alexandre, please put a timestamp in here next time you see this, and we can take a look.

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #4)

Great! Alexandre, please put a timestamp in here next time you see this, and we can take a look.

I did?

(01/07/2020, 10:50 and 17:26 CEST)

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #1)

I saw the webhook come in to the tc-github-web pod, with event-id 3aca6100-bb79-11ea-96b5-4c826c850351 at 2020-07-01 09:00:00.912 GMT.

The logging level on the handlers pod is such that it is not logging further information about handling of pull requests. Can we shift that level down to DEBUG for tc-github in community-tc?

That's 11:00 my time, right when I force-pushed again and that it triggered this time.

Yes, but debug logging wasn't enabled at that time :)

Unassigning since this is not currently actionable..

Assignee: dustin → nobody
You need to log in before you can comment on or make changes to this bug.