Bug 13906 - [QA 3.0.3 RC2] failure in ptest: valgrind.helgrind/tests/tc19_shadowmem
Summary: [QA 3.0.3 RC2] failure in ptest: valgrind.helgrind/tests/tc19_shadowmem
Status: RESOLVED OBSOLETE
Alias: None
Product: Package Testing (ptest)
Classification: QA/Testing
Component: ptest (show other bugs)
Version: 3.0.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 3.0.5
Assignee: Anuj Mittal
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-05-20 03:07 UTC by Sangeeta Jain
Modified: 2020-12-09 06:22 UTC (History)
4 users (show)

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


Attachments
ptest regression report (57.59 KB, application/octet-stream)
2020-05-20 03:07 UTC, Sangeeta Jain
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sangeeta Jain 2020-05-20 03:07:06 UTC
Created attachment 4679 [details]
ptest regression report

Following ptest is failing in current release(3.0.3.rc2) while passing in previous release(3.0.2.rc3): 

ptestresult.valgrind.helgrind/tests/tc19_shadowmem

Regression is performed on ptest results for qemux86-64. 

ptest Results for current release:
https://autobuilder.yocto.io/pub/releases/yocto-3.0.3.rc2/testresults/qemux86-64-ptest/

ptest results for previous release:
https://autobuilder.yocto.io/pub/releases/yocto-3.0.2.rc3/testresults/qemux86-64-ptest/
Comment 1 Richard Purdie 2020-05-21 07:41:47 UTC
I reran the ptest for comparison, results are here: https://autobuilder.yocto.io/pub/non-release/20200521-9/testresults/qemux86-64-ptest/
Comment 2 Anuj Mittal 2020-05-21 19:15:22 UTC
(In reply to comment #1)
> I reran the ptest for comparison, results are here:
> https://autobuilder.yocto.io/pub/non-release/20200521-9/testresults/qemux86-
> 64-ptest/

Thanks Richard. Looks like the test passed this time. I will see if I can reproduce it.
Comment 3 akuster 2020-08-21 17:03:32 UTC
I dont' see this failure in the current test results.

should it be closed.
Comment 4 Anuj Mittal 2020-08-23 17:54:39 UTC
(In reply to comment #3)
> I dont' see this failure in the current test results.
> 
> should it be closed.

I don't know why it was failing in the first place and I think I didn't backport anything so it might still fail under some conditions. 

Perhaps we should close it if there aren't going to be any more zeus releases and this isn't reproducible in dunfell/master builds.
Comment 5 Anuj Mittal 2020-12-09 06:22:20 UTC
This has not happened since on master/dunfell/gatesgarth and zeus is not being actively maintained anymore. So closing.