segmentation fault using jsdom

[bbraun92]

Hey,

I'm running tests using a single-threaded setup and I use jsdom. There's some tests relying on canvas that cause segmentation fault issues running in that mode, most of the tests work fine.
Is there any easy way to configure vitest so that the tests not causing issues are run in a single thread, and the ones causing trouble run in a pool of forks? Does that even make sense?

Thank you

[AriPerkkio]

Yep, canvas doesn't work in node:worker_threads and requires pool: 'forks' in Vitest: #2261 (comment)

You can use poolMatchGlobs to run specific tests in forks pool:

import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    poolMatchGlobs: [
      ['some/path/to/testfile.test.ts', 'forks'],
    ],
  },
})

Or you could just run all tests in single fork instead of single thread, if that's what you want:

import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    poolOptions: { forks: { singleFork: true } },
  },
})

[AriPerkkio]

What Vitest version are you using?

Yes, you can mix poolOptions and poolMatchGlobs like this. You can verify that the file is run correctly by adding console.log('Is forks pool:', process.send != undefined); in my-test.js.

[bbraun92]

I'm on 1.6.0, I'll see if I can verify it thank you!

[bbraun92]

console.log('Is forks pool:', process.send != undefined); logs Is forks pool: false 🤔

[AriPerkkio]

This should help:

    poolMatchGlobs: [
+     [
        '**/test/unit/utils/my-test.js',
        'forks',
+     ]
      ],

[bbraun92]

Oh man, that's a bit embarassing 🙈
Yeah that fixed it, thank you very much!