Confusing CodeQL Error: Go files were found but not processed

Open

#2,515 opened on Oct 2, 2024 5 comments 1 reaction 1 assignee View on GitHub

@mbg is already working on this.

Since Oct 4, 2024.

Assessment

This issue has not been assessed yet.

We are seeing a weird error complaining not all Go files were processed and the error also appears on the default CodeQL scan configuration.

We have some Go files with build tags for testing purposes, for example: https://github.com/linode/terraform-provider-linode/blob/dev/linode/stackscripts/framework_models_unit_test.go#L1, which are the files not included in the scan, but I think it should not trigger an error because generally go build won't build test files (correct me if I'm wrong on this).

Is there any way to get more detailed error message or ignore the error from scanning status reporting?

And I think the correct behavior is to ignore test files not being built in the action.

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.