mistercrunch commented on PR #29771: URL: https://github.com/apache/superset/pull/29771#issuecomment-2261357135
Right, not sure what's up with it, it looks like the job is getting killed, presumably because it's abusing memory usage (?) The confusing thing is we're actually installing less things in the step that fails. I tried a few things already: - setting up swap space, doesn't seem to help, result of following a GPT-generated idea, I'll probably remove that part of the PR - was looking for ways to reduce the parallelism in the docker build, currently it's building the `superset-node` (super memory heavy) while it builds the lean layer (`pip install requirements/base.txt`), but didn't find a clear/easy way to do it. Was looking for either a docker CLI flag or some env var, but nothing seemed to work, GPT hallucinated a few solutions but that didn't work I'm wondering what in this PR is pushing the memory usage (assuming that's why the job gets killed) over the edge, and it seems to indicate that the `master` is probably fragile and on the edge too, meaning that this CI step is likely to fail on master soon too next time we touch something related. Next steps/ideas: - maybe running a docker command to build the superset-node target first, and then push for the other command which would reuse the cached layers from the first command - find some other way to limit parallelism - find a way to get more memory in GHA? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
