nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bitbucket pipeline failed on tests run

Lorenzo Biotti

For a nest.js project I have a pipeline that executes unit and e2e tests.
Locally they run successfully.
In the pipeline, randomly some of them fail due to this error:
"A jest worker process (pid=179) was terminated by another process: signal=SIGKILL, exitCode=null. Operating system logs may contain more information on why this occurred.
at ChildProcessWorker._onExit (../node_modules/jest-worker/build/workers/ChildProcessWorker.js:370:23)"

How can I fix? Where should I check?

Accepted answers

All comments

Theodora Boudale

Hi @Lorenzo Biotti and welcome to the community!

The issue may be related to this bug report I found in the jest repository here:

https://github.com/jestjs/jest/issues/13976

I see that the bug report has been fixed, so you could try using the latest version of jest and see if that fixes the issue.

Just a heads up, other customers have reported that Pipelines builds using the jest framework are hanging or failing because of memory issues.

You can check the following knowledge base article we have created, specifically the section Scenario 2.2: Builds using Jest Test Framework are slow or frequently hang (based on the Pipeline build minutes consumption) or failed with Container “Build” exceeded memory limit error:

https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-pipelines-1141505226.html

The suggestions there might help as well.

Kind regards,
Theodora

bodva

Hey @Theodora Boudale

Unfortunately has the same problem for jest 29.6.2. Could it be that pipelines kill the jest process?

Theodora Boudale

Hi @bodva,

A process may be killed if there is not enough memory. Regular pipelines steps have 4096 MB of memory in total, while large build steps (which you can define using size: 2x) have 8192 MB in total. If you have e.g. 7 jest workers running and each of them is configured to use 2 GB memory, there won't be enough memory for all.

You can check the suggestion in the knowledge base article I shared above:

You can check the following knowledge base article we have created, specifically the section Scenario 2.2: Builds using Jest Test Framework are slow or frequently hang (based on the Pipeline build minutes consumption) or failed with Container “Build” exceeded memory limit error:

https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-pipelines-1141505226.html

If that doesn't help you can create a ticket with the support team via https://support.atlassian.com/contact/.

Kind regards,
Theodora

bodva

Hey @Theodora Boudale

Thanks for the replay.

I am working with option maxWorkers = 2 to avoid the case with a memory limit.

I don't receive a memory limit problem.

My problem is the same as the topic starter has.

I checked the article you linked and found no solution to my problem.

I am using 1x steps. And the most unexpected thing here is that sometimes it killed unit tests, sometimes e2e. And in some runs - it works.

bodva

@Lorenzo Biotti

If you are still experiencing the problem, you could review the discussion under the previous comment.

We had the same errors as you had, and we found two ways:

You could migrate to "swc" instead of ts-node and add the custom runtime "@side/jest-runtime".
You could set "size: 2x" for the step when experiencing this issue.

With the first approach, you can avoid substantial memory leaks, which have a combination of node > 16.11 and jest.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines