Fix Node.js + Docker issue preventing MW 1.30 (EXDEV: cross-device link not permitted, rename) #949
Comments
|
Summarizing the error linked at the top of the, {
"changed": true,
"cmd": "cd /etc/parsoid && npm install",
"delta": "0:00:32.072253",
"end": "2018-03-26 14:05:30.266723",
"msg": "non-zero return code",
"rc": 238,
"start": "2018-03-26 14:04:58.194470",
"stderr": "<<< See STDERR section for text >>>",
"stderr_lines": [ "same", "as", "stderr", "but", "as", "array" ],
"stdout": "<<< See STDOUT section for text >>>",
"stdout_lines": [ "same", "as", "stdout", "but", "as", "array" ]
}STDERRSTDOUT |
|
Possible solutions I've come up with so far based on reading other issues:
|
|
Fixed by using Node 8.x |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The main holdup for MW 1.30 on meza at this point is the fact that automated testing fails due to some conflict between Docker (which is used as a testing platform) and Node.js. See example failed build here:
https://travis-ci.org/enterprisemediawiki/meza/builds/332081440
The meat of the error is:
Unfortunately I got side-tracked from this issue for a couple months and I'm just getting some of my notes into an issue. IIRC, the reason for the failure is due to Docker's file system and Node.js method of moving a file.
List of related links:
The text was updated successfully, but these errors were encountered: