beetmover-repackage-macosx64-shippable/opt jobs end up in claim expired due to OoM
Categories
(Release Engineering :: Release Automation, defect)
Tracking
(Not tracked)
People
(Reporter: eijebong, Assigned: eijebong)
References
Details
Failing task
Pod logs: https://cloudlogging.app.goo.gl/F4zXtYnoVChPD6B8A
Node logs: https://cloudlogging.app.goo.gl/c3NiJdec2eiPNgb58
Job: https://firefox-ci-tc.services.mozilla.com/tasks/W0Q-8ajDTfORbrFzc6L9KA/runs/0
pod name: beetmover-prod-relengworker-firefoxci-gecko-3-1-86749b46b6hxjdf
Gets OOM'ed at 800MB RAM usage.
Most recent task of the same kind that succeeded (on the same deployment...):
Job: https://firefox-ci-tc.services.mozilla.com/tasks/HtbU5bN_Td2KOYlLKe0sNg
Pod logs: https://cloudlogging.app.goo.gl/PfUFebKGDnA7eKc29
pod name: beetmover-prod-relengworker-firefoxci-gecko-3-1-5d45f6c8f49ch7f
Gets up to ~740MB RAM usage at its peak
|
Assignee | |
Comment 1•6 months ago
|
||
I bumped the memory limit up by 200 MB since I couldn't figure anything wrong with the code (we have releases that pass and one that doesn't, but the ones that do pass are very close to the limit). If it fails again over the next few days because of this then I'll dig deeper but right now I'm going to call this fixed as the latest nightly didn't have any beetmover related issues.
Description
•