-
I would like to have a little assistance in why this particular scenario is not working. Deploy Currently even if the retry has failures, all steps are made to go green. During the check the only step allowed to fail is the initial test publish, but the retry should not be allowed to fail as we want to catch if tests fail on the retry. check:
if: always()
needs:
- upload-first-run-tests
- upload-retry-run-tests
runs-on: Ubuntu-latest
steps:
- name: Decide whether the needed jobs succeeded or failed
uses: re-actors/alls-green@release/v1
with:
allowed-failures: upload-first-run-tests
jobs: ${{ toJSON(needs) }} Any help on solving this issue would be hugely appreciated |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Wild guess — you have a |
Beta Was this translation helpful? Give feedback.
Wild guess — you have a
continue-on-failure
somewhere in that job. If that's the case, then GitHub sets the job status to success. You may want to get familiar with the differences of theoutcome
vs.conclusion
— one is the actual result and the other is how GH treats it (and it is ultimately controlled bycontinue-on-failure
value — on job or step level).This also correlates with the green checkmarks in the left sidebar next to the listed jobs.
For this action to know that a job has failed, it shouldn't pretend to pass. The action cannot look into what's happening inside the job because GitHub does provide access to such a context.
FWIW if you have a public CI run / configs, I can take …