Bug 10490 - Error on oeqa.runtime.rpm.RpmInstallRemoveTest when running testimage
Summary: Error on oeqa.runtime.rpm.RpmInstallRemoveTest when running testimage
Status: VERIFIED NOTABUG
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-tools (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.3 M2
Assignee: Jose Perez C
QA Contact: Juan Ramos
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-24 16:38 UTC by Jose Perez C
Modified: 2017-01-06 22:00 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Log from genericx86-64_NUC (14.98 KB, text/plain)
2016-10-24 19:27 UTC, Juan Ramos 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Perez C 2016-10-24 16:38:17 UTC 
STATUS: IDLE
BUILD: 2.2.rc4(M4): 4b94b498e21aeba945fe7e72a6b7c4bb0314fb83
ENVIRONMENT: genericx86-64-lsb on NUC and MM64
STEPS TO REPRODUCE: 

-------
1. Add belo info to the conf/local.con file 
   INHERIT += "testimage"
   TEST_TARGET = "simpleremote"
   TEST_SERVER_IP = "HOST ip" --> IP of the machine being used to launch tests
   TEST_TARGET_IP = "DUT ip"  --> IP of the device under test
   TEST_SUITES = " auto"
   DISTRO = "poky-lsb" 
2. Run ` $ bitbake core-image-lsb-sdk -c testimage `

Expected Result:
No errors should be reported on the log results 

Actual Result
======================================================================
ERROR: setUpClass (oeqa.runtime.rpm.RpmInstallRemoveTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jframo1x/pokylsbx86-x64/meta/lib/oeqa/runtime/rpm.py", line 37, in setUpClass
    oeRuntimeTest.tc.target.copy_to(os.path.join(rpmdir,testrpmfile), "/tmp/rpm-doc.rpm")
UnboundLocalError: local variable 'testrpmfile' referenced before assignment
Comment 1 Juan Ramos 2016-10-24 19:27:13 UTC 
Created attachment 3491 [details]
Log from genericx86-64_NUC
Comment 2 Markus Lehtonen 2017-01-05 14:11:55 UTC 
I don't have a NUC (or similar system) myself so I haven't been able to reproduce this. Are you able to reliably reproduce this yourself, i.e. is it happening every time? If so, are you able to reproduce this in qemux86-64 image?

The bug looks strange, though, as if the rpm-doc package is missing from DEPLOYDIR.
Comment 3 Jose Perez C 2017-01-05 15:53:53 UTC 
(In reply to comment #2)
> I don't have a NUC (or similar system) myself so I haven't been able to
> reproduce this. Are you able to reliably reproduce this yourself, i.e. is it
> happening every time? If so, are you able to reproduce this in qemux86-64
> image?
> 
> The bug looks strange, though, as if the rpm-doc package is missing from
> DEPLOYDIR.

Seems like this was a transient issue.. actually this bug was not appearing in 2.2 rc6 this means is not present in morty neither in the most recent validation for 2.3 M1. So closing the bug, will reopen if we see it again on subsequent QA cycles.
Comment 4 Juan Ramos 2017-01-06 22:00:06 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > I don't have a NUC (or similar system) myself so I haven't been able to
> > reproduce this. Are you able to reliably reproduce this yourself, i.e. is it
> > happening every time? If so, are you able to reproduce this in qemux86-64
> > image?
> > 
> > The bug looks strange, though, as if the rpm-doc package is missing from
> > DEPLOYDIR.
> 
> Seems like this was a transient issue.. actually this bug was not appearing
> in 2.2 rc6 this means is not present in morty neither in the most recent
> validation for 2.3 M1. So closing the bug, will reopen if we see it again on
> subsequent QA cycles.

Verified, not present in 2.3M1 logs.