L10n jobs on 2.0 and beta failing due to bad hg clones

RESOLVED FIXED

Status

P1
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [l10n])

(Assignee)

Description

8 years ago
I have clobbered the slave manually and put it back into the pull.

I will keep it open to check it is all back to normal.
How did it burn them?
Whiteboard: [l10n] → [l10n][slaveduty]
configure was borked, which usually dates back on a failed hg clone.
ok, all yours, armen.
Whiteboard: [l10n][slaveduty] → [l10n]
Today it's w32-ix-slave26.
Let's address the underlying problem, then.
Summary: win32-slave13 burned a bunch of L10n jobs on 2.0 and beta → L10n jobs on 2.0 and beta failing due to bad hg clones
(Assignee)

Updated

8 years ago
Priority: -- → P1
(Assignee)

Comment 6

8 years ago
linux64-ix-slave17 is now at fault.
Armen, presumably this isn't the same bug, unless there's something correlating disk failure and l10n jobs.  Rather, I assume that since there are so many l10n jobs, they just happen to flush out slave failures more often than other jobs.

Can we close this bug, and file new bugs for each failed slave (as has already been done for the above slaves)?
(Assignee)

Comment 8

8 years ago
(In reply to comment #7)
> Armen, presumably this isn't the same bug, unless there's something correlating
> disk failure and l10n jobs.  Rather, I assume that since there are so many l10n
> jobs, they just happen to flush out slave failures more often than other jobs.
> 
> Can we close this bug, and file new bugs for each failed slave (as has already
> been done for the above slaves)?

That was the original purpose of this bug to deal with win32-slave13.

I have only dealt with linux-ix-slave17 (bug 648528).

Once I check the other two slaves I will file their own bugs and close this one.
(Assignee)

Comment 9

8 years ago
I don't have enough information for w32-ix-slave26.
I have clobbered nevertheless.

We will have to tackle new individual issues on new bugs.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.