Closed Bug 493152 Opened 11 years ago Closed 11 years ago

Run our own hg mirror server for the build farm

Categories

(Mozilla Messaging :: Server Operations, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gozer, Unassigned)

Details

Just to decouple ourselves from hg.mozilla.org.
It's up and running, and I've already seen this interesting failure from it:

 Traceback (most recent call last):
   File "/var/apache2/htdocs/hgwebdir.cgi", line 47, in <module>
     wsgicgi.launch(application)
   File "[site-packages]/mercurial/hgweb/wsgicgi.py", line 65, in launch
     application(environ, start_response)
   File "[site-packages]/mercurial/hgweb/hgwebdir_mod.py", line 74, in __call__
     self.run_wsgi(req)
   File "[site-packages]/mercurial/hgweb/hgwebdir_mod.py", line 121, in run_wsgi
     hgweb(repo).run_wsgi(req)
   File "[site-packages]/mercurial/hgweb/hgweb_mod.py", line 221, in run_wsgi
     method(self, req)
   File "[site-packages]/mercurial/hgweb/protocol.py", line 96, in changegroupsubs    chunk = f.read(4096)
   File "[site-packages]/mercurial/util.py", line 1491, in read
     for chunk in self.iter:
   File "[site-packages]/mercurial/localrepo.py", line 1857, in gengroup
     prune_filenodes(fname, filerevlog)
   File "[site-packages]/mercurial/localrepo.py", line 1786, in prune_filenodes
     clnode = cl.node(filerevlog.linkrev(n))
   File "[site-packages]/mercurial/revlog.py", line 526, in linkrev
     return self.index[self.rev(node)][4]
   File "[site-packages]/mercurial/revlog.py", line 522, in rev
     raise LookupError(node, self.indexfile, _('no node'))
 mercurial.revlog.LookupError: data/accessible/src/base/nsAccessibilityAtoms.h.i@b807d720f68f: no node
It's now running successfully, with one cheat in place. For l10n repositories, since there are a lot of them (and they are small), I opted to just proxy requests for l10n-central (and releases/l10n-mozilla-1.9.1 back to the orignal hg.mozilla.org to simplify the mirroring jobs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.