You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Team - We are observing that Bitbucket runners are getting crashed because of allocation failure. Could you please help on how to handle this issue? Attached screenshots for reference.
Automation tool used for regression: Cypress
Cypress tool Version : 12.0.0.
Hi Rajan and welcome to the community!
Steps that run on Atlassian infrastructure get 4 GB of memory unless you use size: 2x. With size: 2x, a step gets 8 GB of memory, which is the maximum that can be configured for builds running on our infrastructure.
If a step is running on a self-hosted runner, you can also configure size: 4x or size: 8x so that the step gets 16 GB or 32 GB of memory respectively (if the host machine has that memory available).
This is the documentation for the size option:
If you have a service container in a step, it gets by default 1024 MB of memory unless you specify a different limit. In case it is a service that needs more memory and not the build container, you can configure more memory for the service.
If you are using a Linux Docker self-hosted runner, please make sure you disable swap and configure vm.swappiness on the host machine as per this guide.