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
The user options undefined message is not an issue.
The issue is that your source_files param in the JSON your integration is sending to the Coveralls API is empty:
'{"source_files":[],
(Second line from the bottom of your CI build log.)
This happens when the integration can't find the source files listed in your LCOV report (in each SF: /path/to/file.ext entry).
And that's usually because there's a discrepancy between the file paths in your LCOV file and the source file paths at Github, relative to the root directory of your repo.
Assuming you're using the Coveralls Github Action (which uses the node-coveralls integration under-the-hood, you can use the base-path option to correct for that.
@afinetooth Thank you, I have not solved, but I realized the issue is not related to coveralls. I don't use GitHub actions, think the problem is related to nyc that produces odd paths like: src/utilities/file:/mnt/software/Progetti/OSEventListener/src/utilities/NullLogger.ts
I reply here in case someone has the same issue. The problem was caused by a bug in ts-node version 10.8.1, if you upgrade to the last version the problem is fixed.
I have a problem on my project, for some reasons coveralls is unable to detect the coverage report: https://coveralls.io/builds/51472302
Below a complete log of run in verbose mode, I launched it locally, but from CI the problem is the same.
The only issue that I see in log is: [debug] "2022-08-08T17:23:06.293Z" 'user options undefined', but I am not sure if it's a problem.
What am I doing wrong:
The text was updated successfully, but these errors were encountered: