circleci test_static consumes OOM

Current behavior 😯

Regularly seeing test_static circleci jobs fail because of OOM issues.

example: https://app.circleci.com/pipelines/github/mui/mui-toolpad/3578/workflows/b14c82c8-b004-45c1-b1ca-5a30412b6154/jobs/13481

@mui/toolpad-app: [build:*next] Killed
@mui/toolpad-app: [build:*next] error Command failed with exit code 137.
@mui/toolpad-app: [build:*next] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@mui/toolpad-app: [build:*next] yarn run build:next exited with code 137

Insights confirmed an increase in max memory consumption since Sept 30

Might be caused by https://github.com/mui/mui-toolpad/pull/1043. I’m putting my money on the source map changes 🙂

We were already quite close to 100%, so if we can’t bring memory consumption down, scaling the instance may be in order.

[Janpot]

Sentry should not be generating sourcemaps, it should only upload them, our build is suppose to generate sourcemaps, so that would mean disabling sourcemaps for our build

The sentry plugin wraps the next.js config and alters it to so that our build generates sourcemaps in production and then it uploads them at the end of the build.

I think what we could do is:

• set productionBrowserSourceMaps in the next.js config to make sure sourcemaps are generated in our build (sentry plugin should do it under the hood as well but let’s not rely on that).
• set hiddenSourceMaps to false in the Sentry plugin to make sure our sources contain a sourceMappingURL directive. We want this so that we can debug in production, and so that the Sentry backend can locate them as well
• set dryRun to true to avoid Sentry from uploading the sourcemaps to their backend after the build

[bytasv]

Sentry should not be generating sourcemaps, it should only upload them, our build is suppose to generate sourcemaps, so that would mean disabling sourcemaps for our build