500246 - Reset hg repo used by TryServer

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

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

[Chris Cooper [:coop] (he/him)]

Re-assigning to server ops. Aravind took care of this last time (bug 491092).

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(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.

Comment 3

[matthew zeier [:mrz]]

over to releng for date/time.

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Totally fair - I'll take this and will figure out what time works best with dev.

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Already sorted this out in real-life; Aravind can do this in tonight's downtime

Comment 6

[Aravind Gottipati [:aravind]]

Done, try server should be clean now.

Comment 7

[Armen [:armenzg]]

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.

Comment 8

[Reed Loden [:reed]]

(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

[Chris Cooper [:coop] (he/him)]

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.

Comment 10

[Armen [:armenzg]]

(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.