Hello Chen, But the test still attempts to run rpm on the target. I can't understand how target rpm can be available on the image, but at the same time target rpm-doc package is not available in rpm deploy dir.
The issue is probably that the test should simply be skipped (in the same way that dnf testcases are skipped - please refer to them), if there is no package management on target? Like this: @skipIfNotFeature('package-management', 'Test requires package-management to be in IMAGE_FEATURES') Alex 2018-06-14 10:29 GMT+03:00 ChenQi <qi.c...@windriver.com>: > On 06/14/2018 02:57 PM, Alexander Kanavin wrote: >> >> 2018-06-14 7:52 GMT+03:00 Chen Qi <qi.c...@windriver.com>: >>> >>> The test cases assume that rpm-doc is built out, as it says it its >>> comment. This is not always true. And it sometimes results in >>> following error. >>> >>> | cls.tc.target.copyTo(test_file, dst) >>> | UnboundLocalError: local variable 'test_file' referenced before >>> assignment >> >> Wait, you need to explain this further. What is the situation when it >> isn't true? >> >> Alex >> > > Hi Alex, > > For any image that does not have rpm installed, rpm package is not likely to > be built out. > Having PACKAGE_CLASSES set to "package_rpm" will only ensure rpm-native to > be built out. > > Best Regards, > Chen Qi -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core