File not found

[lays147]

Hi @vladopajic !

As of the latest version of the action, I'm having an issue on my CI. The job is failing with the error:

failed to generate coverage statistics: could not find file [github.com/myorg/my-app/app/middlewares/mocks/rabbitmq_acknowledger.go]

When I run the latest bin locally, I don't have any issue. Any tips on how to debug this issue?
Because the file is on the PR related to this action run, so I don't know why this error is happening.

Also, the job doesn't fail when that error is generated, so when the following steps try to access the report, it ends in an error.

Thanks!

[vladopajic]

hey,

could you check to see which version has started to cause trouble? instead of using v2 use full version v2.13.1 (start from this version and reduces down until it works).
hint: you can use that version, which works, until issue is resolved (if any).

additional check if setting source-dir will work:
source-dir: /github/workspace (if i understand correctly your case). source dir should be relative path from root (where action is executed) to root dir of source (same dir where go.mod file is at).

[lays147]

Well, I did the tests up until the version 2.12.0(the project moved to go version 1.24 and got an error). And the issue persists. Idk what could be wrong, because up to a week ago the pipeline was running without issues.

Also, setting source dir does not change the outcome. =/

However, I do think that the action should exit !=0 when an error occurs, so the pipeline does not continue. Right now is exiting 0, and the next steps that depends on the outcome of this one runs and fails.

[vladopajic]

because up to a week ago the pipeline was running without issues.

i did push new release v2.13.1, that was supposed to improve file search on windows machines. you are saying that v2.13.0 is not working as well? if that's true then i guess it must be something due to:

• source-dir because that was introduce in that release,
• or local-prefix, is was removed in #168 - now it is automatically obtained by reading go.mod file, if it fails to read it then it might also be causing problems.

i'll have a look in this, but there is not much information for me to properly debug.

---

However, I do think that the action should exit !=0 when an error occurs, so the pipeline does not continue.

it is doing so here:

go-test-coverage/main.go

Line 175 in b1d7f32

os.Exit(1)

maybe you have continue-on-error: true?

[vladopajic]

i have pushed new release v2.13.2, it has debug printf that will tell us if module directive is correctly read.
please let me know outcome of running v2.13.2. thanks <3

[lays147]

@vladopajic I don't have continue on error. As for the screenshot, you can see that the action is indeed exiting 0.

The bug is not reproducible in the latest version.

[vladopajic]

oh nice!

but i am curious to know what the issue was.
can you check your go.mod file and tell me if there is any white space at the start of the line with the module github.com/org/project directive?

[lays147]

Nope:

module github.com/myorg/my-app

go 1.24.2

[vladopajic]

hmm.. okay, not really sure what have caused it. but anyway i am closing this issue since it is not replaceable anymore.

thank you for all the effort! happy coding 🌞