Bug 11224 - Compliance: LTP, POSIX, LSB tests are not creating results file (.targz)
Summary: Compliance: LTP, POSIX, LSB tests are not creating results file (.targz)
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.4 M1
Assignee: dengke
QA Contact:
URL:
Whiteboard: Backport to 2.3.1
Depends on:
Blocks:
 
Reported: 2017-03-23 00:54 UTC by Juan Ramos
Modified: 2017-05-02 09:04 UTC (History)
6 users (show)

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

Attachments
.targz path not created screenshot (2.55 MB, image/jpeg)
2017-03-23 01:03 UTC, Juan Ramos 		no flags Details
compliance_test.py (2.32 KB, text/plain)
2017-03-23 16:56 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 Juan Ramos 2017-03-23 00:54:39 UTC 
Steps to reproduce:

1) Download lsb image from autobuilder( same image as in LSB weekly testing for genericx86-64-lsb bsp)

* we test compliance on NUC with genericx86-64-lsb, core-image-lsb-sdk

2) Install the image on DUT

3) Configure the network so it be able to work externally:

- Export the proxy using "export http_proxy=<add your proxy link>" command eg
$ export http_proxy=http://proxy-chain.intel.com:911

And check if you have internet connection, typing on terminal:

* There is a bug and if you make these steps in another order than above, it may be possible not work

4) Copy "compliance_test.py" script on DUT

- Make the script executable: "chmod a+x compliance_local.py"

- Run in command line the following command:
 ./compliance_test.py <milestone> <date>" 


Expected Results: Logs created and 18 MB File: /var/opt/lsb/test/manager/results/x86.../x86....targz 

Actual Result: Logs are created but neither /results/x86.../x86... folder or .targz file are created.
Comment 1 Juan Ramos 2017-03-23 01:03:04 UTC 
Created attachment 3662 [details]
.targz path not created screenshot
Comment 2 Juan Ramos 2017-03-23 16:56:05 UTC 
Created attachment 3664 [details]
compliance_test.py
Comment 3 Juan Ramos 2017-04-04 16:24:42 UTC 
this issue is present in 2.3 M3 rc2
commit 415b72ffcbd26e5f3664370d8b2a9b8105fb6342
Comment 4 dengke 2017-04-21 04:21:00 UTC 
Hi Juan
I have solve the problem, this is because the rpm packages didn't install successfully, such as:
  lsb-setup-4.1.0-1.noarch.rpm
  lsb-dist-checker-5.0.0.1-1.targetarch.rpm
  ......
After the change of rpm in oe-core, when we install those packages directory, it show the following information:
  package lsb-setup-4.1.0-1.noarch is intended for a different operating system
So we should add the option "--ignoreos" to the rpm install command in LSB_Test.sh in ./meta/recipes-extended/lsb/lsbtest, in this we can make sure the correct install of the above rpm packages.