Skip to content

FailFastPublishUnitTestResults

publish-unit-test-result-action should fail fast.

Defined by FailFastActionsRule which supports workflows, actions in the "Default" ruleset along with FailFastUploadArtifact, FailFastPeterEvansCreatePullRequest, FailFastSoftpropsGhRelease.

Description

EnricoMi/publish-unit-test-result-action should be configured to fail the CI when no test results are found.

When the action is not configured to fail on inconclusive results, the action step will be successful even when the test results are missing.

It will emit a warning:

Warning: Could not find any JUnit XML files for .../TEST-*.xml

which is easy to miss. This means that the CI could be broken by PRs, even if the job is required on a branch protection rule.

See the action_fail_on_inconclusive input declaration.

In case you're certain this if acceptable behavior, disable this by explicitly setting action_fail_on_inconclusive: false.

Compliant example

action_fail_on_inconclusive input is specified.

example.yml 

on: push
jobs:
  example:
    runs-on: ubuntu-latest
    steps:
      - uses: EnricoMi/publish-unit-test-result-action@v2
        with:
          action_fail_on_inconclusive: true
          junit_files: |
            **/build/**/TEST-*.xml

Non-compliant example

action_fail_on_inconclusive is not declared, so it uses the default false value.

example.yml 

on: push
jobs:
  example:
    runs-on: ubuntu-latest
    steps:
      - uses: EnricoMi/publish-unit-test-result-action@v2
        with:
          junit_files: |
            **/build/**/TEST-*.xml

  • Line 6: Step[EnricoMi/publish-unit-test-result-action@v2] in Job[example] should have input action_fail_on_inconclusive: true.