Closed
Bug 1186797
Opened 11 years ago
Closed 9 years ago
valgrind jobs are not using bundleclone
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: glandium, Unassigned)
Details
Probably not the right component but at least I know the right person will see it.
The valgrind jobs are cloning from mercurial from *inside* the mock environment, contrary to other jobs (although I think some static analysis/hazard/js builds do the same, or at least used to).
And since bundleclone is not available there... this is what happens:
command: output:
*** failed to import extension bundleclone from /usr/local/lib/hgext/bundleclone.py: [Errno 2] No such file or directory: '/usr/local/lib/hgext/bundleclone.py'
Traceback (most recent call last):
File "/tools/python27-mercurial/lib/python2.7/site-packages/mercurial/extensions.py", line 100, in loadall
load(ui, name, path)
File "/tools/python27-mercurial/lib/python2.7/site-packages/mercurial/extensions.py", line 74, in load
mod = loadpath(path, 'hgext.%s' % name)
File "/tools/python27-mercurial/lib/python2.7/site-packages/mercurial/extensions.py", line 54, in loadpath
return imp.load_source(module_name, path)
IOError: [Errno 2] No such file or directory: '/usr/local/lib/hgext/bundleclone.py'
Comment 1•11 years ago
|
||
This feels like a bug to get bundleclone installed inside the chroot. I know this has been discussed before. Might be a dupe of another bug.
Component: Mercurial: bundleclone → General Automation
Product: Developer Services → Release Engineering
QA Contact: catlee
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•