Workflow failing without logs or "Re-run" button

https://github.com/trassir/conan-center-index/pull/187/checks?check_run_id=670363468

For some reason, there sometimes appear two builds for the same job in the workflow, with one failing silently and not providing “Re-run jobs” button, unlike any normal failed jobs.

Screenshot_2020-05-13_13-56-27.png

Said failed job also is not displayed in global workflow list, but instead displayed in the PR status, preventing it from being merged peacefully due to “build failing”.

Screenshot_2020-05-13_14-02-34.png

@artalus ,

Based on the matrix you set in the workflow, it should only generate matrix jobs with the below 2 configurations:

1) libpng (linux-gcc8, 1.6.37)

{
  "build": "linux-gcc8",
  "libpng_versions": "1.6.37",
  "os": "ubuntu-latest",
  "compiler": "gcc",
  "compiler_version": "8",
  "docker_image": "trassiross/conan-gcc8",
  "build_types": "Release",
  "archs": "x86_64"
}

2) libpng (macos, 1.6.37)

{
  "build": "macos",
  "libpng_versions": "1.6.37",
  "os": "macos-10.15",
  "build_types": "Release",
  "archs": "x86_64",
  "compiler": "apple_clang",
  "compiler_version": "11.0",
  "xcode_version": "11.3.1"
}

I also forked your repository and tested on my side, it could work as expected, no extra matrix job generated (see here).

This may be a temporary issue, please try again on your side to see if the issue still exists. Any update, please feel free to tell us.

In addition, when a workflow run is triggered by the pull request event, in the runs list on the Actions tab, the displayed title of this run is the PR’s title. However, if you click the title to open the details page of this run, the displayed title in the upper left corner is the commit message.
So, actually that workflow run has been listed on the Actions tab, as I have marked in the below image:

@brightran wrote:

I also forked your repository and tested on my side, it could work as expected, no extra matrix job generated (see here).

This may be a temporary issue, please try again on your side to see if the issue still exists. Any update, please feel free to tell us.

It is indeed not an easily reproducible issue, but I already encountered it before with another PR and another workflow. Alas that PR was force-pushed to another commit, so the old run link I posted to our local chat went stale and I couldn’t provide any screenshots - but the symptoms were the same; a job with the same matrix parameters present as succeeded and failed without any “re-run” button.

My working theory is that it might be somehow related to another PRs being merged while the current one is still processed. So like, if there are PRs A and B that trigger the same workflow X, with A changing X, and A is being merged while checks in B are still running, then B might theoretically misunderstand something and trigger some excessive build in X.

I will update the post if it happens a third time.

@artalus ,

My working theory is that it might be somehow related to another PRs being merged while the current one is still processed. So like, if there are PRs A and B that trigger the same workflow X, with A changing X, and A is being merged while checks in B are still running, then B might theoretically misunderstand something and trigger some excessive build in X.

Each workflow run has only one  commit ref , and GitHub only references the workflow YAML file (jobs, steps, and other configurations set in the YAML file) on that commit ref to generate and execute this workflow run.

When workflow-X is running (suppose we call it X-run-A ) with the commit ref commit-A , if you change some configurations in the YAML file of workflow X to generate a new commit ref commit-B , the  X-run-A  will not reference the new configurations on  commit-B , it still reference the configurations on  commit-A. GitHub will reference the YAML file on commit-B to generate a new run of  workflow-X (suppose we call it X-run-B ).

So, generally the new commits will not affect the running workflow runs.