You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We lost code coverage tracking for the C code in the migration from Travis CI to GitHub Actions in PR #28.
I verified in the logs that all files are compiled and linked with the --coverage option. But in the logs uploaded to Codecov, the "reduced" coverage info is zero. E.g. for standalone/lib/fsawa.c we get
...
==> Running gcov in . (disable via -X gcov)
./standalone/lib/nfa.gcda:cannot open data file, assuming not executed
./standalone/lib/fsageopairs.gcda:cannot open data file, assuming not executed
./standalone/lib/diffredwl.gcda:cannot open data file, assuming not executed
./standalone/lib/fsarevmid.gcda:cannot open data file, assuming not executed
./standalone/lib/fsasubmult.gcda:cannot open data file, assuming not executed
...
Cannot open source file fsa.c
Cannot open source file nfa.c
Cannot open source file fsageopairs.c
Cannot open source file diffredwl.c
Cannot open source file fsarevmid.c
...
File 'fsawa.c'
Lines executed:40.91% of 330
Branches executed:43.57% of 280
Taken at least once:31.79% of 280
Calls executed:22.89% of 83
Creating 'fsawa.c.gcov'
...
Cannot open source file fsasubmult.c
Cannot open source file kbfns.c
Cannot open source file migmdet.c
Cannot open source file fsawa.c
...
So I am guessing it is confused about how to find the source files. But I wonder why?!? Esp. since it used to work fine when we used basically the same scripts on Travis... weird.
The text was updated successfully, but these errors were encountered:
We lost code coverage tracking for the C code in the migration from Travis CI to GitHub Actions in PR #28.
I verified in the logs that all files are compiled and linked with the
--coverage
option. But in the logs uploaded to Codecov, the "reduced" coverage info is zero. E.g. forstandalone/lib/fsawa.c
we getyet also
In the build logs, we see:
So I am guessing it is confused about how to find the source files. But I wonder why?!? Esp. since it used to work fine when we used basically the same scripts on Travis... weird.
The text was updated successfully, but these errors were encountered: