Bug 13713

Summary: [QA 3.1 M1 RC8] glib failure in ptest
Product: [QA/Testing] Package Testing (ptest) Reporter: Sudhir Sharma <sharmasudhir>
Component: ptestAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: akuster
Version: 3.1   
Target Milestone: 3.1 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
ptest regression results
none
ptest report for current release none

Description Sudhir Sharma 2019-12-17 03:35:29 UTC
Created attachment 4604 [details]
ptest regression results

We took ptest results from autobuilder and did ptest regression. 

1. Download ptest results for current and previous release.
2. Run resulttool regression for ptest
3. Identify test that passed previous release and failed  this release

Previous release 
https://autobuilder.yocto.io/pub/releases/yocto-3.0.rc2/testresults/qemux86-64-ptest/testresults.json

Current release
https://autobuilder.yocto.io/pub/releases/yocto-3.1_M1.rc8/testresults/qemux86-64-ptest/testresults.json

We have observed failure in ptest regression results.

Attaching failure log for glib and valgrind.

glib
ptestresult.glib-2.0.glib/option-argv0.test: FAILED -> PASSED 

valgrind
ptestresult.valgrind.drd/tests/std_list: FAILED -> PASSED
Comment 1 Sudhir Sharma 2019-12-17 03:36:33 UTC
Created attachment 4605 [details]
ptest report for current release
Comment 2 Ross Burton 2020-02-03 17:31:31 UTC
From the latest ptest report:

            "ptestresult.glib-2.0.glib/option-argv0.test": {
                "status": "PASSED"
            },