Share via

SIGTERM causing our Nx Runners to fail in Azure Pipelines

Jack Lazenby 20 Reputation points
2023-10-18T10:00:25.3533333+00:00

We have some Nx runners in our pipeline to help manage our CICD builds. They have looked at this issue and they believe it is an issue that Microsoft needs to support us with rather than them.

Since upgrading to the latest version of Nx, when building our largest projects, we encounter this error:

Error:
   Agent 'Agent 63940' exited with the error: Agent was terminated via SIGTERM.

This error has only started since updating Nx and we wonder if something is spiking memory usage or something like that?

I can attach our logs if easier but wanted to know if anyone else has encountered this issue?

Community Center | Not monitored

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.