Reset hg repo used by TryServer

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
8 years ago
2 years ago

People

(Reporter: joduinn, Assigned: aravind)

Tracking

Details

When the hg repo for TryServer gets too many heads, we end up having problems with pushlog, and general slower TryServer performance. We reset the hg repo on 07may2009, so I think its time to reset the repo again.

Comment 1

8 years ago
Re-assigning to server ops. Aravind took care of this last time (bug 491092).
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz

Updated

8 years ago
Assignee: server-ops → aravind
(In reply to comment #1)
> Re-assigning to server ops. Aravind took care of this last time (bug 491092).

ok, but we have to schedule a downtime for this. It means taking down the TryServer to do this.
(Assignee)

Updated

8 years ago
Flags: needs-downtime+
Whiteboard: Waiting for build to give us a date to work on this.

Comment 3

8 years ago
over to releng for date/time.
Assignee: aravind → nobody
Component: Server Operations → Release Engineering
Flags: needs-downtime+
QA Contact: mrz → release
Totally fair - I'll take this and will figure out what time works best with dev.
Assignee: nobody → joduinn
Already sorted this out in real-life; Aravind can do this in tonight's downtime
Assignee: joduinn → aravind
Component: Release Engineering → Server Operations
QA Contact: release → mrz
Whiteboard: Waiting for build to give us a date to work on this.
(Assignee)

Comment 6

8 years ago
Done, try server should be clean now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
The try server was not responding to changes send by developers. This required a reconfigure of the master.

The master was looking for changes in:
http://hg.mozilla.org/try/pushlog?fromchange=fae93ca5b23249537e6805797f2a638633b94efe&tipsonly=1
with message:
"revision not found: ��<��2IS~hy*c�3�N�"
and after the reconfigure is looking in:
http://hg.mozilla.org/try/pushlog?fromchange=2a00e3cb6f6940319b953a2b8cf7b81270f5d068&tipsonly=1

Please for the next reset check that the changes column on the waterfall to see if everything is OK or push a change to the try server and see if it gets picked up.
(In reply to comment #7)
> Please for the next reset check that the changes column on the waterfall to see
> if everything is OK or push a change to the try server and see if it gets
> picked up.

What waterfall? Also, IT doesn't usually push changes to any VCS in general. Maybe somebody from RE should be around after this is done to ensure that part gets done.

Comment 9

8 years ago
I don't think Armen was implying that IT do this. This was more a reminder for RelEng to do exactly as you say because, IIRC, we had exactly this same issue last time we reset the try repo.
(In reply to comment #9)
> I don't think Armen was implying that IT do this. This was more a reminder for
> RelEng to do exactly as you say because, IIRC, we had exactly this same issue
> last time we reset the try repo.
>
Thanks coop. Yeah, exactly what he said. Preserving the comment for the next reset will help.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.