Skip to content

Unit-tests not registering as a fail #16

Answered by webknjaz
spongeBri asked this question in Q&A
Discussion options

You must be logged in to vote

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 the outcome vs. conclusion — one is the actual result and the other is how GH treats it (and it is ultimately controlled by continue-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 …

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@spongeBri
Comment options

@webknjaz
Comment options

Answer selected by webknjaz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants