Open
Bug 1363491
Opened 7 years ago
Updated 7 years ago
Failure in create-test-environment: rbweb failing to install npm
Categories
(Developer Services :: General, task)
Developer Services
General
Tracking
(Not tracked)
NEW
People
(Reporter: sfink, Unassigned)
Details
Attachments
(2 files)
224.90 KB,
text/plain
|
Details | |
1.93 KB,
patch
|
Details | Diff | Splinter Review |
I attempted again to get the testing environment set up for bzexport (see also: bug 1199037). With some convincing, it made it quite a ways, but ended up saying rbweb> Error unpacking rpm package npm-1.3.6-5.el6.noarch
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Reporter | ||
Comment 3•7 years ago
|
||
The latter changes were because (1) coverage failed to install, complaining about its hash; and (2) I got an error about there being no such version for mercurial 4.0.2.
Reporter | ||
Comment 4•7 years ago
|
||
It looks like the setup made it far enough that running the bzexport tests works, which is all I cared about. \o/
Comment 5•7 years ago
|
||
When it downloads coverage, what's the filename? I wonder if you are running a 32-bit Python by chance...
Comment 6•7 years ago
|
||
There are patches in bug 1363509 to add *optional* docker support to the new hgdev environment. That should be enough to unblock you on running bzexport tests.
You need to log in
before you can comment on or make changes to this bug.
Description
•