Closed Bug 768622 Opened 12 years ago Closed 12 years ago

Please reset the try repo at 20:00 PDT tonight (2012-06-26)

Categories

(Developer Services :: General, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: fox2mike)

References

Details

(Whiteboard: [buildduty][downtime])

As discussed in the relops mtg today (and announced to the newsgroups: https://groups.google.com/d/topic/mozilla.dev.planning/EMmLOCZntAs/discussion), please reset the hg try repo at 20:00 PDT tonight (2012-06-26).

Bear (and coop) will be around on the releng side to assist with closing try and such.
Blocks: 767657
Assignee: server-ops-devservices → shyam
Does this mean that everyone will lose their try pushes?  Can't we just strip the changeset which caused bug 767657?
(In reply to Ehsan Akhgari [:ehsan] from comment #1)
> Does this mean that everyone will lose their try pushes?  Can't we just
> strip the changeset which caused bug 767657?

I think releng has tried that with not much improvement. Instead of slowing down try for everyone, we felt it was better to reset it and ensure it works better vs having continual problems.

This is in progress.
Complete :

[root@hgssh1.dmz.scl3 scripts]# time ./reset_try.sh 
Deleting the current try repo
Cloning mozilla-central into the try repo
Fixing try repo permissions
Cleaning up pushlogdb
Syncing changes into the tmpfs repo
All done

real    59m25.712s
user    0m5.863s
sys     0m27.272s

PS : Even though the script says Deleting current, I've only moved it away.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Timeline (all times are PDT):

1944 - philor closed the try tree for non-repo reasons
2000 - down time started
2038 - fox2mike starts the try reset script
2110 - fox2mike reports script running and is in the clone step
2144 - fox2mike reports done
2145 - philor informed that try reset is done and he will open the trees
2147 - bear confirms that try tree is open
had to restart the schedulers so that new try pushes were handled

philor discovered this during post-downtime sanity-checks and discovered that we had to do this previously as outlined in bug 732666

I asked Callek to update the buildduty notes
Whiteboard: [buildduty][downtime]
Depends on: 768807
bug 768847 might be a follow up from this bug.
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.