Bug 12446 - [pyro] the gzip packages are not shown in the table they appear in 0 and slang will not run in ptest
Summary: [pyro] the gzip packages are not shown in the table they appear in 0 and slan...
Status: RESOLVED OBSOLETE
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3.3
Hardware: NUC x86_64
: Medium critical
Target Milestone: 2.7
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-12-21 15:52 UTC by oscar lopez arandas
Modified: 2019-05-17 20:15 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
FULL-LOG (5.32 MB, application/octet-stream)
2017-12-21 15:52 UTC, oscar lopez arandas
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description oscar lopez arandas 2017-12-21 15:52:31 UTC
Created attachment 4163 [details]
FULL-LOG

the gzip packages are not shown in the table they appear in 0 and look for them in the log if they appear that the run and slang do not run in ptest, in the log nothing of slang appears

https://wiki.yoctoproject.org/wiki/Ptest_022df4653576c72752156bef8fda0e1aa46733d2
https://wiki.yoctoproject.org/wiki/Ptest/archive

poky :  022df4653576c72752156bef8fda0e1aa46733d2 
2.3.3.rc1
HW: NUC  6i5SYH
image:https://autobuilder.yocto.io/pub/releases/yocto-2.3.3.rc1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg

STEP TO REPRODUCE:
Test Process 
1. Download pTest image from autobuilder( you can find core-image-sato-sdk image in pTest directory)
   * Test are applied on NUC with genericx86-64 

2. Install the image on DUT (using legacy boot)
   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://<my_proxy>:<port>
   - And check if you have internet connection, typing on terminal:
     $ wget www.google.com

3. In command line type
   $ ptest-runner > ptest.log
     and wait for it to finish ( about 5 hours)
     Note: The "script" is already placed on the distro, you just have to type ptest...TAB and the terminal should autocomplete the command.
     and > ptest.log, in order to save the test results in that file.


[edit]  Reporting Process 

1. Generate the report of pTests as follows: 
    1.1 Get the log from the DUT.
    1.2 Go to the Ptest/archive page and check the previous execution to this release.
    1.3 Go the the report of the execution and download the log.
    1.4 Use the ptest-parser script to generate the report, this script generates a file called <release>wiki.page.
    1.5 Create a wiki with the name Ptest_<commit-tested>
    1.6 Copy the content of the content of <release>wiki.page and paste it on new wiki created.
    1.7 Upload the log of current execution and update the recent created wiki with the link to the log.
    1.8 Check the packages that had regression on pass rate Down rate.png and if there is a bug reported update the bug with comments that still present 
        on current commit, if there is no bug created raise a new one.
    1.9 Update the Ptest/archive wiki with the info of this new execution.

expect outcome:
all passrate increased 

actual oucome:
gzip packages are not shown and  slang will not run in ptest

NOTE:
FULL-LOG IN ATTACHMENT
Comment 1 Ross Burton 2019-05-17 20:15:54 UTC
The ptest reporting has been rewritten entirely, closing.