Closed Bug 1616738 Opened 5 years ago Closed 5 years ago

[github] Fenix taskcluster jobs finished but status doesn't update in the github commit log

Categories

(Taskcluster :: Services, task)

Product:
Taskcluster
Component:
Services
Platform:
Other
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: rpapa, Assigned: bstack)

References

(Blocks 1 open bug)

Details

The fenix taskcluster jobs have completed successfully over 10 hours ago, but status hasn’t yet updated in the github commit log. It says “Some checks haven’t completed yet”

See PRs marked with a yellow dot indicating 'queued':https://github.com/mozilla-mobile/fenix/commits/master

Click on queued job:
https://github.com/mozilla-mobile/fenix/runs/456052518
Still shows in progress.

However, click on Task Group and it shows that job has actually COMPLETED:
https://firefox-ci-tc.services.mozilla.com/tasks/groups/ZJL4DPKNSDOBbRDNH2Ul1g

Flags: needinfo?(bugzeeeeee)

It looks like some of the UI test jobs are completing now and the correct completed status is making it's way to the github commit log. However, the jobs that were marked 'queued' from yesterday are still indicating that incorrect status.

Thank you for filing this! I will investigate when I have a moment

Assignee: nobody → bugzeeeeee
Flags: needinfo?(bugzeeeeee)
Summary: Fenix taskcluster jobs finished but status doesn't update in the github commit log → [github] Fenix taskcluster jobs finished but status doesn't update in the github commit log
Blocks: github-bugs
Assignee: bugzeeeeee → bstack
Status: NEW → ASSIGNED

There was a github outage at about the time this was reported. Has this reoccurred since that time? I would like to blame them if not.

I'm going to make sure our logging is in good shape for this so that we can more easily debug this for next time.

Flags: needinfo?(rpappalardo)

(In reply to Brian Stack [:bstack] from comment #3)

There was a github outage at about the time this was reported. Has this reoccurred since that time? I would like to blame them if not.

I'm going to make sure our logging is in good shape for this so that we can more easily debug this for next time.

Hi Brian, WFM. Yea, something to be able to clearly discern what's going on when outages happen would be great. thank you! Feel free to close

Flags: needinfo?(rpappalardo)

Thank you for the investigation bstack! I am closing this. The bug to track the logging improvement is here

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.