Thibault Charbonnier
Thibault Charbonnier
Currently this has stalled our workflow and ability to make progress in our work, we have half a dozen PRs that are stalled because they can't produce a coverage report...
> We suspect that you may have only updated the action version (`@v2`) on your coverage report step, and did not update it on your (close) parallel build / webhook...
After a few days of use in our `main` branch, I'm reporting back with some updates on how I've seen this workflow behave, and wondering if there is still a...
It has been happening again this afternoon. As we have been moving GitHub Actions workflows to "reusable jobs", I had been force-pushing refinements to a branch attached to a PR...
> I'm just not super familiar with the use case of "reusable jobs" as you referred to it here. Can you point me to a doc or something? Yes, [reusable...
Looking at this again, I'm starting to suspect "coverage" (or the "Coveralls Finish" step) might not be "reusable" and should be extracted out of the reusable job file and be...
That worked! But only after adding: ``` env: COVERALLS_SERVICE_NUMBER: ${{ github.run_id }}-${{ github.run_attempt }} ``` to _both_ of `ci.yml` and `job-unit-test.yml`, top-level each, as it env variables are not inherited...
Hello! I feel bad for hijacking this issue, but I am facing a similar problem that we can't seem to get rid of. I remain dumbfounded as to what the...
Can we restart the CI on this one? I don't think the failures are related; and we'd really like this being part of the next release if possible so that...
Ah, excellent, done!