Could not find file

[hisarbalik]

After bumping the version to v2.14.1, I am facing the issue on github action. The job failed with the following error:

{"Threshold":75,"Path":"^internal/resourcelock$"},{"Threshold":84,"Path":"^internal/webhookcert$"},{"Threshold":85,"Path":"^webhook
{"level":"error","error":"could not find file [github.com/my-org/my-project/apis/operator/v1alpha1/telemetry_types.go]","message":"failed to generate coverage statistics"}

When I run it locally, the issue is not present.

There is a screenshot from CI:

The file causing the issue is excluded

exclude:
  # Exclude files or packages matching their paths
  paths:
    - ^apis

It seems to be similar to #178

[vladopajic]

@hisarbalik hey! could you use v2.14.2 and report with debug output? this version has more information in debug and it may be useful to us here.

thanks!

[hisarbalik]

Here is the debug output of v.2.14.2

/home/runner/work/my-org/my-project/bin/go-test-coverage --config=./.testcoverage.yml --debug=true


{"level":"info","message":"running check..."}
{"level":"info","config":{"Profile":"cover.out","Debug":true,"LocalPrefixDeprecated":"","SourceDir":"","Threshold":{"File":0,"Package":90,"Total":0},"Override":[{"Threshold":80,"Path":"^internal/validators/secretref$"},{"Threshold":75,"Path":"^internal/resourcelock$"},{"Threshold":84,"Path":"^internal/webhookcert$"},{"Threshold":85,"Path":"^webhook
{"level":"debug","module":"github.com/my-org/my-project/docs/user/integration/sample-app","message":"using module directive"}
{"level":"error","error":"could not find file [github.com/my-org/my-project/apis/operator/v1alpha1/telemetry_types.go]","message":"failed to generate coverage statistics"}
-------------------------
Running coverage check failed.
Error: failed to generate coverage statistics: could not find file [github.com/my-org/my-project/apis/operator/v1alpha1/telemetry_types.go]
Please use `--debug=true` flag to see detailed output.
make: *** [Makefile:157: check-coverage] Error 1
Error: Process completed with exit code 2.

[vladopajic]

hey @hisarbalik, please check with v.2.14.3.

issue was automatically closed, please reopen issue and provide new logs if you still experience issues. :)

[hisarbalik]

Thanks @vladopajic, the issue was fixed with version v2.14.3