Coveralls shows 0% coverage for a matrix CI workflow on GitHub

[LinqLover]

Here is one of the erroneously calculated builds: https://coveralls.io/builds/40758673 However, all other current builds look identically. Note that the CI passes on GitHub and the local TestRunner in my image attests me a 50% coverage. In particular, note that in the past™ it already had worked: https://coveralls.io/builds/40745486

In that earlier build, I had fail-fast enabled and some jobs failing, but could this make a difference?
Does smalltalkCI handle parallel runs or do I have to use the coverallsapp action manually as described in the docs?

[LinqLover]

PS: Is there an option to optimistically merge all coverage data for platform-specific code branches or would coveralls do this for me automatically? :)

[fniephaus]

I vaguely remember adding a parallel flag and that CI would need to tell coveralls specifically about the completion of a build unit:

smalltalkCI/helpers.sh

Line 422 in 79bbab1

local parallel="${COVERALLS_PARALLEL:-}"

I'm afraid I don't have any answers for your questions. If you could explore and improve the docs, that would be great.

[LinqLover]

I added the COVERALLS_PARALLEL to my build but this didn't help. I'm also confused because on this repository, the coverage has always been detected correctly ... Is this really non-deterministic behavior and based on the order of job execution? 🤔

[fniephaus]

It's very much possible that the order is important. If you could debug this that'd be great!

[gcotelli]

For coveralls I'm using the official GitHub action and see no problems with the coverage reporting. Take a look for example at https://github.com/ba-st/Launchpad/blob/release-candidate/.github/workflows/unit-tests.yml and https://github.com/ba-st/Launchpad/blob/release-candidate/.smalltalkci/.unit-tests.ston

…

On Tue, Oct 26, 2021, 08:49 Fabio Niephaus ***@***.***> wrote: It's very much possible that the order is important. If you could debug this that'd be great! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#536 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQCK6BNNLDZHAA75PZI7H3UI2PUNANCNFSM47CLCJPQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.