Upgrading to LCOV 2.1 yields an unknown error

[albinahlback]

At FLINT, we've been trying to upgrade LCOV from version 2.0 to the newly released version 2.1. We have yet been unable to identify the problem that Codecov has with this, and no proper error code can seen on Codecov.

The process in our CI is as follows:

1. We have a library written in C,
2. We compile it with appropriate C flags in GCC to be able to obtain code coverage,
3. We run tests,
4. We use LCOV as opposed to gcov (or something similar) in order to suppress certain lines,
5. We use codecov-action along with a token to push it to our Codecov account.

For a working run with LCOV 2.0, see this.

However, for LCOV 2.1, we have a runner showing no signs of error. After the runner is done, we simply get an error on Codecov saying the reason for the failed upload being Null.

Now, obviously this is not a good error message because it doesn't state what is wrong. Furthermore, I opened an issue at LCOV (https://github.com/linux-test-project/lcov/issues/289) regarding this, but I came to the conclusion that the difference of outputs on my local up-to-date Arch Linux machine for LCOV 2.0 versus LCOV 2.1 was none.

Any guess to why this is? Why is no proper error message shown?

[drazisil-codecov]

Hi @albinahlback ,

Are you able to add the --dry-run flag to the CLI command so I can see what is getting uploaded? It looks like gcov is still running, so it might be doing something strange. The error is expired report, which is a cobertura error, not an lcov one, so I wonder if you are upload two diffent reports.

[covecod[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[albinahlback]

Will come back to this.