Closed Bug 1290930 Opened 8 years ago Closed 8 years ago

Bm 128 and bm 129 hung reconfig, no alert.

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1273249

People

(Reporter: Callek, Unassigned)

Details

callek@Centaurus:~/mozilla/obj/reconfig/tools/buildfarm/maintenance$ for i in 128 129; do ssh root@buildbot-master129.build.mozilla.org "ls -la /builds/buildbot/tests1-windows/reconfig.lock"; done
-rw-rw-r-- 1 cltbld cltbld 0 Aug  1 06:40 /builds/buildbot/tests1-windows/reconfig.lock
-rw-rw-r-- 1 cltbld cltbld 0 Aug  1 06:40 /builds/buildbot/tests1-windows/reconfig.lock


(This was after I was manually doing a reconfig today to support merge day)
Email alerts did go out to release+buildduty@mozilla.com.
Ahhh, I hadn't seen the alerts in #buildduty
relengbot hasn't been functional since... March? There's a bug open that alin was working on last I knew.
(In reply to Amy Rich [:arr] [:arich] from comment #3)
> relengbot hasn't been functional since... March? There's a bug open that
> alin was working on last I knew.

Indeed, I'm working on a fix for that. Marking this as a dupe.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.