opkg ptest shows now results: https://autobuilder.yocto.io/pub/non-release/20190529-5/testresults/testresult-report.txt A quick check suggests this is because the output doesn't follow our format so no PASS/FAIL/SKIP values are seen, hence the zero counts. We may need to pipe the output of the tests through sed.
Razi, Thanks for taking a Newcomer bug. Let us know here, on the mail list or on IRC (freenode #oe #yocto) if you need anyone to bounce ideas off of. Once you have a fix, take a look at: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Your commit will likely need to be sent to: openembedded-core@lists.openembedded.org ../Randy
Razi, How are you doing with this defect? Feel free to document your analysis here in the defect log if you think that will help. ../Randy
(In reply to comment #2) > Razi, > How are you doing with this defect? > Feel free to document your analysis here in the defect log if you think that > will help. > ../Randy Hi Rany, It is state as NEWCOMER bug, but there is no description on how to reproduce the bug. I am diving into Yocto to understand better not specifically this bug but in general how it works. It took me time, but no worries, I will manage to send the fix soon. Regards, Razi
Sounds good. Thanks for working on it. I haven't looked at the ptest-runner but as Richard said, the opkg ptest-runner likely needs to be changed to produce a result in the format expected. Here's a ptest doc once you are ready to check that out: https://wiki.yoctoproject.org/wiki/Ptest Try out something that works like running the gzip ptests first; then work on opkg. The expected gzip ptest result is: Recipe | Passed | Failed | Skipped | Time(s) -------------------------------------------------------------------------- acl | 222 | 0 | 0 | 2 apr | 44 | 0 | 0 | 57 ... gzip | 22 | 0 | 0 | 3 ... From: https://autobuilder.yocto.io/pub/non-release/20190709-1/testresults/testresult-report.txt https://autobuilder.yocto.io/pub/non-release/
I am working on this issue but not intensively. In the report from the new release, I see that opkg passed the ptest successfully. http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.8_M2/testreport.txt Is it already fixed?
Seems to be fixed now, likely by: http://cgit.openembedded.org/openembedded-core/commit/?id=76a7f0d60f5dc38da15f21720cb97bf761562b44 opkg-utils: upgrade to version 0.4.1 - Drop 0001-opkg-build-do-not-set-mtime-on-data.tar.X.patch - Drop 0001-opkg-list-fields-fix-to-print-the-fields-again.patch Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> This is based on the test logs, it's fixed as of: https://autobuilder.yocto.io/pub/non-release/20190717-7/testresults/testresult-report.txt Broken up to around: https://autobuilder.yocto.io/pub/non-release/20190715-6/testresults/testresult-report.txt
Re-closing. Razi, if you have reason to re-open it please say so, and don't change the target milestone: M2 is in the past, so we'd need a time machine.
It was fixed in 2.8 M2, so I just wanted to reset it to the version recently released. :)
Unfortunately you re-opened it too. :)