Bug 10458

Summary: devtool: npm add for cute-files module fails due to error in recipetool
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Henry Bruce <henry.bruce>
Component: devtools / tool chainAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Undecided CC: meta.mr.watcher, meta.watcher
Version: 2.1.2   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
evtool-failure-krogoth.log none

Description Henry Bruce 2016-10-19 16:44:53 UTC
Created attachment 3480 [details]
evtool-failure-krogoth.log

Run command
devtool add "npm://registry.npmjs.org;name=cute-files;version=1.0.2"

Expected behavior
-----------------
Command completes without error.


Observed behavior
-----------------
Command fails to due to recipetool error
ERROR: Command 'recipetool --color=always create -o /tmp/devtoolIAfX5H "npm://registry.npmjs.org;name=cute-files;version=1.0.2"  -x /path/to/build/workspace/sources/devtoolsrcnkkCVA' failed:
(For full log see attached file devtool-failure-krogoth.log)

Note: command completes OK with Yocto 2.2
Comment 1 Paul Eggleton 2016-10-19 20:23:48 UTC
The error isn't being handled too well if it doesn't mention why it's failing, so that's one problem I can look into. However I can't seem to reproduce the failure itself, though perhaps it may be dependent on what version of nodejs is being used.
Comment 2 Henry Bruce 2016-10-19 20:58:08 UTC
I used the krogoth meta-oe layer so versions are as follows:
node: 4.4.3
npm: 2.15.1
Comment 3 Henry Bruce 2016-10-19 22:04:04 UTC
One possible clue
* In krogoth build environment, open a devshell for nodejs-native
* Download ttps://github.com/martinaglv/cute-files/archive/master.zip
* Unzip
* cd cute-files-master
* npm install --production
See a segmentation fault.

The above procedure completes successfully on my build host if I don't run it in krogoth build environment. Versions are as follows:
node: 4.5.0
npm: 2.15.9
Comment 4 Paul Eggleton 2016-10-20 02:47:42 UTC
OK, so I had failed reading comprehension earlier and missed that it was krogoth. I retried with krogoth (on a different machine) and found that unfortunately I still can't reproduce it.

Segfaulting implies that something really bad happened inside node - can you reproduce this on another machine? Also, I wonder if simply upgrading the version of nodejs would fix it.
Comment 5 Henry Bruce 2016-10-20 05:19:16 UTC
I repeated test on a different machine using the crops/poky container and it worked OK. I'm guessing my system has some host contamination. Sorry for false alarm.

I'll close as "not a bug"