Hey guys has anyone seen this before when running builds on seed?

● Test suite failed to run
    jest: failed to cache transform results in: /tmp/jest_0/jest-transform-cache-ba6890a420e1a6b5180fa098b09849d2-d1d5bfaad8659acd06069518d3e76e6c/96/tradelevelmodel_9674fbffebca9dba9f1d9df31330d70e.map
    Failure message: ENOMEM: not enough memory, write
      at writeFileSync (node_modules/write-file-atomic/index.js:215:10)
      at writeCacheFile (node_modules/@jest/transform/build/ScriptTransformer.js:792:33)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:537:7)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:569:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:607:25)

Just started today I’m wondering if I’m doing something wrong in my tests as it seems I’m running out of memory. I don’t have many at the moment. 48 total but the

sst test

command seems to take a long time on the type checking portion (45 seconds) then it throws these errors.

Hey @colin, did this start happening all of a sudden today?

heya frank yeah ill bump the build machine to see if it helps. And yeah I haven’t seen this error before today which is odd

Yeah give the Medium machine a try.