Encountering SIGBUS intermittently

Hey – regarding this https://github.com/swc-project/swc/discussions/9996

Encountering the following error on CI but unable to reproduce it locally, when using

@swc/jest

@swc/jest

@swc/jest

@swc/jest:

  ● Test suite failed to run
    A jest worker process (pid=X) was terminated by another process: signal=SIGBUS, exitCode=null. Operating system logs may contain more information on why this occurred.

  ● Test suite failed to run
    A jest worker process (pid=X) was terminated by another process: signal=SIGBUS, exitCode=null. Operating system logs may contain more information on why this occurred.

  ● Test suite failed to run
    A jest worker process (pid=X) was terminated by another process: signal=SIGBUS, exitCode=null. Operating system logs may contain more information on why this occurred.

  ● Test suite failed to run
    A jest worker process (pid=X) was terminated by another process: signal=SIGBUS, exitCode=null. Operating system logs may contain more information on why this occurred.

Hunch is that SIGBUS started showing up since using swc since it's the only thing that changed at that time, also it is more likely to have access to lower level memory constructs than Node.

Any thoughts? Help appreciated!

GitHub

SIGBUS error with @swc/jest: Intermittent CI failures · swc-project...

Hello

We're experiencing an intermittent issue with @swc/jest that's causing our CI builds to fail. We switched from babel-jest to @swc/jest for transpiling our TypeScript project in uni...

kdy1•2/6/25, 9:28 AM

You should not use jest-worker with SWC

Kkdy1 You should not use jest-worker with SWC

mewxieOP•2/6/25, 10:38 AM

What do you mean? jest-worker is being used internally by jest right?