Deploy failure: timeout at the end of webpack build

Questions and Answers Deployment
1

As of 3 hours ago our deploys seem to time out then fail at the end of webpack build. We didn’t change anything on our side in terms of build config or env. We’ve been able to deploy with no issues previously.

Build: 25a75c3d-35d9-4345-a1b7-5aab4f77aacc-1169 builds normally (Webpack build successful!)
Build: 25a75c3d-35d9-4345-a1b7-5aab4f77aacc-1170 the issue starts

The build process runs as expected, then we hit “Command still running” at the end which seems to loop indicating some sort of timeout or connection err:

`#18 167.5 [sentry-webpack-plugin] Info: Successfully uploaded source maps to Sentry`
3753 10 Oct, 19:40:14.82 `Command still running. No output available. Waiting for next line...`
3754 10 Oct, 19:42:14.95 `Command still running. No output available. Waiting for next line...`
3755 10 Oct, 19:44:15.07 `Command still running. No output available. Waiting for next line...`

I’ve tried it a few times, same result. There’s no build error or anything else I can see so not very clear what’s happening. I thought it might be sentry-related so I set sentry to dry-run, same issue.

Did anything change on the Qovery side that might impact this? Or is there anything you’re able to see log-wise we can’t? thanks

Application: https://console.qovery.com/organization/828d9c2c-fd72-4b4e-ab58-71de40ecfdd2/project/bb20c0dc-13d3-481e-9f73-3c7bece44017/environment/25a75c3d-35d9-4345-a1b7-5aab4f77aacc/services/general

2

Hello @ChrisBolman1 ,

I’m Charles-Edouard, TAM @Qovery,

I’ll check your problem with the team and get back to you.

Regards,
Charles-Edouard

3

Thanks @ce_gagnaire. We believe this issue is resources-related. We tried and tested a few more things this morning. By reducing the number of chunks in the webpack build and fine-tuning a few other things we were able to get the app to deploy using a sequential build, i.e., for (const chunk of chunks){ ... reduce + run }

We’d ideally like to do a parallel build but this doesn’t seem possible with available resources:


`#18 366.6 <--- JS stacktrace --->`
3327 11 Oct, 08:54:22.98 `#18 366.6 `
3328 11 Oct, 08:54:22.98 `#18 366.6 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`
4

Hello @ChrisBolman1 ,

Thank you for the update.

It does look like a resource problem.

Can you try adding this to your Dockerfile please?

export NODE_OPTIONS=--max-old-space-size=14,192

This can help prevent OOM errors.

Please let me know if this was helpful.

5

Hello @ChrisBolman1,

Does this solution work for you?

Please let me know if you need any help on this topic.

Regards,
Charles-Edouard

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.