IMAGE USED: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120730-2/machines/emenlow/core-image-sato-emenlow-20120730042252.hddimg Quicky is not installed in the e-menlow sato image: root@emenlow:~/abat# which quicky root@emenlow:~/abat# quicky -sh: quicky: command not found
Is quicky supposed to be installed on all sato images?
Tom, Is quicky is supposed to be part of core-image-sato ? I guess not. Then, what is the recommended way to get quicky in the image for testing ?
I don't know - you'd have to follow the dependency chains of what's included in the image to know. If not and you need it for testing, I'd guess just use one of the standard mechanisms for including packages in images to put it there?
Tom, Then we need to find out how PRC QA people used quicky. Whom do we ask this question in PRC ?
I think Jiajun did this, but maybe Shane is the only one left to ask at this point? Not sure, but Song should have a handle on who to ask about QA questions, so I would ask him to coordinate. I'm surprised there wasn't a knowledge transfer between PRC and Romania to cover all this (and also to transfer hardware).
Jiajun, Shane, Song, Can you help here with the knowledge transfer from PRC QA team to Romania QA team? Thanks, Nitin
Jiajun, Shane, Song, please respond to the comments on this bug. Thanks, Nitin
(In reply to comment #7) > Jiajun, Shane, Song, please respond to the comments on this bug. Thanks, > Nitin Hi Nitin, We should only test quicky in sato-sdk image, not sato image.
Alexandru, I think Jiajun's answer closes the bug. In the future for such kind of QA bugs make sure to CC Jiajun, so that such kind of misunderstandings can be avoided earlier. Thanks, Nitin
Ok, Thanks for the info, Alex.