runner: Badge always incorrectly displayed as "failing"
This badge is shown as “failing” but the tasks’ statuses are all green.
Describe the bug The badge was green since CD pipeline is prechecked before running, meaning it normally should never fail. The badge for it was green and it suddenly went to red - “failing”, even though all constituent tasks are succeeding.
To Reproduce See 1st paragraph.
Expected behavior The badge is green when all tasks successful, red when at least one fails.
Runner Version and Platform
Full yaml snapshot available here.
Simplified yaml:
on:
push:
tags:
- '[0-9]+.[0-9]+.[0-9]+'
workflow_dispatch: # Run with Run Workflow button in GitHub Action Job.
inputs:
is_manual_cd:
default: true
description: Manual trigger
jobs:
common-assertions:
runs-on: ubuntu-latest
OS of the machine running the runner?
Linux
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 10
- Comments: 33 (5 by maintainers)
I wish GitHub was 100% Free/Libre and open-source software, then skilled hackers from all around the world could fix this problem.
I removed all previous runs on
mainand successfuly got a green badge.Not anymore, the irony.
From what I understand, the ELS issue is outside the scope of the runner itself. @ruvceskistefan and I don’t have the full context of the ELS issue since we both primarily work on the runner itself.
I asked around to other teams and it looks like the root cause is an int32 overflow on the search index. 😭 There will be an incident review internally for this error and repair items to make sure this won’t happen again.
@mihaigalos do you mind if I close this runner issue since the issue is truly out of scope for the runner? 🙇
You can post to https://github.community/c/code-to-cloud/github-actions/41 if you need more info or RCA about the ELS issue.
Works - deleted all previously failed runs. Thanks, @mihaigalos @wireless90
@mihaigalos, I’m glad that it worked for you. I’ll close this issue, if you are still getting the same error you can reopen it.
Love how these update regardless of what you said. Both now show no status.
@mihaigalos Your
mainbranch didn’t run the workflow for the past few months, and the last time it runs was failed.Makes sense, I’ll reopen it and we’re going to investivate the root cause.