The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

[Kshitij-Katiyar]

My repo has codeQL go analysis enabled and was working fine until a few weeks ago.
no it fails with the following error
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

Logs show no error everything seems to work fine except the below line, which I think is unrelated

2024-11-05T12:25:48.3087301Z 2024/11/05 12:25:48 Makefile found. 2024-11-05T12:25:48.3088372Z 2024/11/05 12:25:48 Trying build command make [] 2024-11-05T12:26:09.5990096Z : No names found, cannot describe anything.

[jketema]

Hi @Kshitij-Katiyar,

It's very difficult to tell what is going on from the information you provided. Could you share a link to the repository on which this is happening?

[Kshitij-Katiyar]

@jketema Sure, https://github.com/mattermost/mattermost-plugin-jira
Let me know if you are able to look into the action logs

[jketema]

Thanks. I have access to the logs. It looks like the Go analysis started failing when we rolled out CodeQL 2.19.2. I'll loop in the responsible engineering team.

[Kshitij-Katiyar]

Thank you so much, @jketema. Let me know if you need any more help from us.
I'm hoping for a quick fix on this one.

[Kshitij-Katiyar]

Hey @jketema, have you informed the engineering team responsible for this issue?

[jketema]

Yes, they're looking into this.

[Kshitij-Katiyar]

Yes, they're looking into this.

@jketema Thanks for the update

[mbg]

Hi @Kshitij-Katiyar 👋🏻

I am on the engineering team that supports Go for CodeQL. I have looked at your repo and what's going on in your CodeQL runs.

Fundamentally, there's no difference in what is happening in the successful runs and the ones that are now failing consistently, except that the latter crash when running /home/runner/work/mattermost-plugin-jira/mattermost-plugin-jira/bin/golangci-lint run ./.... That's part of your Makefile and our Go autobuilder invokes that (this hasn't changed).

What I can observe, however, is that bin/golangci-lint now appears to consume excessive amounts of memory (160GB+ during my test). The Actions runner doesn't have nearly that much memory, so it runs out of memory, crashes, and the workflow fails.

If I run a system-wide version of golangci-lint on your codebase (v1.55.0), it works fine. However, if I run the version of golangci-lint that your Makefile installs (v1.51.1) and then run that on your codebase, it exhibits the excessive memory usage. In your main CI, it seems like you may also be installing v1.55.2, which also works fine.

In any case, this suggests that there is an issue with v1.51.1 of golangci-lint when used on your codebase. I would suggest updating your Makefile to pin a newer version. That should resolve the issue with your CodeQL workflow.

Alternatively, if you don't want to pin a newer version of golangci-lint there or pinning the newer version doesn't help, you could also:

1. Modify your CodeQL workflow to use a manual build command, instead of relying on the autobuilder, and then run a more specific build command that avoids running make check-style and golangci-lint.
2. Change your Makefile so that check-style is not run by default.

[Kshitij-Katiyar]

Hi @Kshitij-Katiyar 👋🏻

I am on the engineering team that supports Go for CodeQL. I have looked at your repo and what's going on in your CodeQL runs.

Fundamentally, there's no difference in what is happening in the successful runs and the ones that are now failing consistently, except that the latter crash when running /home/runner/work/mattermost-plugin-jira/mattermost-plugin-jira/bin/golangci-lint run ./.... That's part of your Makefile and our Go autobuilder invokes that (this hasn't changed).

What I can observe, however, is that bin/golangci-lint now appears to consume excessive amounts of memory (160GB+ during my test). The Actions runner doesn't have nearly that much memory, so it runs out of memory, crashes, and the workflow fails.

If I run a system-wide version of golangci-lint on your codebase (v1.55.0), it works fine. However, if I run the version of golangci-lint that your Makefile installs (v1.51.1) and then run that on your codebase, it exhibits the excessive memory usage. In your main CI, it seems like you may also be installing v1.55.2, which also works fine.

In any case, this suggests that there is an issue with v1.51.1 of golangci-lint when used on your codebase. I would suggest updating your Makefile to pin a newer version. That should resolve the issue with your CodeQL workflow.

Alternatively, if you don't want to pin a newer version of golangci-lint there or pinning the newer version doesn't help, you could also:

1. Modify your CodeQL workflow to use a manual build command, instead of relying on the autobuilder, and then run a more specific build command that avoids running make check-style and golangci-lint.
2. Change your Makefile so that check-style is not run by default.

Hey @mbg, I tried upgrading and degrading the golangci-lint version but I did not helped me. You can have look on this PR
Any other suggestions

[mbg]

Hi @Kshitij-Katiyar,

It looks like you tested v1.51.0 and v1.51.2, which are only minor version changes compared to the problematic version. I didn't test those, but it's likely that they have the same issue as v1.51.1. Could you try one of the v1.55.x versions that worked for me?

[Kshitij-Katiyar]

Hi @Kshitij-Katiyar,

It looks like you tested v1.51.0 and v1.51.2, which are only minor version changes compared to the problematic version. I didn't test those, but it's likely that they have the same issue as v1.51.1. Could you try one of the v1.55.x versions that worked for me?

@jketema @mbg Thanks for your support and prompt responses. It works fine for me at v1.55.0.
Again thank you for your support

[jketema]

Closing as resolved.