If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add task or code to clean up the Windows builders

RESOLVED WORKSFORME

Status

Release Engineering
Platform Support
RESOLVED WORKSFORME
2 years ago
a year ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
I had to gracefully shutdown b-2008-ix-0170 because it was burning jobs for the release.

The first failure:
http://buildbot-master86.bb.releng.scl3.mozilla.com:8001/builders/b2g_mozilla-b2g34_v2_1s_win32_gecko%20build/builds/1/steps/clone_buildtools/logs/stdio
There's probably something we can dupe this against already, or it goes away when we have fully switched to runner.

In this case there was a 'WINNT 6.1 x86-64 cypress build' job which ran out of space while packaging tests. It asked for 12G and got 12.4G. Probably just need to ask for more.
(Reporter)

Comment 2

2 years ago
This happened again for today's beta release.
This time the marionette job failed when the previous automation job didn't. The ui_update_verify jobs don't seem to be making sure there is sufficient free space.
Assuming that moving to AWS has fixed this. Re-open if that's not true.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.