Everyday we found bug with "out of memory" in pipline. And obvious our tests are failed everytime
And if you try to retry several times it could pass successfully
notices like:
ENOMEM: not enough memory, read
ENOMEM: not enough memory, mkdir '/opt/atlassian/pipelines/agent/build/.tmp/jest-cache/quick/jest-transform-cache-2dbe71a10f0904bba3645b00ee1882ab-8b8a495612ac4adb0e70b598728540c1/1b'
How we can fix it ?
Could you give more info on what kind of build you doing?
Same issue for a Java project, look my answer here: https://community.atlassian.com/t5/Bitbucket-questions/Pipelines-memory-limit-exceeded/qaq-p/578984/comment-id/16283#M16283
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.