[yocto] QA cycle report for 2.3.2 rc1

Cruz, Libertad libertad.cruz at intel.com
Thu Sep 21 16:42:52 PDT 2017


Hello All,



Here is the current report for the 2.3.2 rc 1 point release test cycle.

Full Report :  https://wiki.yoctoproject.org/wiki/WW38_-_2017-09-20-_Full_Test_Cycle_-_2.3.2_rc1

======= Summary ========

During QA cycle for point release 2.3.2 rc1 one new bug was opened. Bug 12114<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12114> [4] is about the GDC AB Ubuntu 17.04 worker having resource issues, therefore testing for this distribution is blocked.



The following bugs were tagged to the test runs but none of them block functionalities.

Bug 11879[1] is about uvesafb errors present in the minnowmax log and is tagged to this test cycle because the fix is in 2.4 M4 but not in 2.3.2 rc1.

Bug 10455[2]  is in progress design and targeted to milestone 2.5.

Bug 10477[3] is also targeted to be done on 2.5.



LPT/Compliance results for point releases are not documented. So 2.3.2 rc1 results should be the same as the 2.3 M4 release. If this were not true then Windriver would investigate and raise a bug.


Performance
Perf results does not shows many changes compared to 3.2.1, there is only a little regression of 6% building roofs on Fedora machine, the rest of the numbers are almost the same.





Ubuntu  15            Test          2.3.1_rc2            2.3.2_rc1             %

                              sato           1:14:04              1:12:11               -2.54

                              rootfs        2:39                    2:49                     6.29

                              rmwork     1:04:49              1:04:15               -0.87

                              kernel        5:25                    5:21                    -1.23

                              eSDK          2:42                    2:46                     2.47





Fedora   23           Test          2.3.1_rc2            2.3.2_rc1             %

                              sato          1:13:17              1:14:51               2.14

                              rootfs       2:41                    2:45                    2.48

                              rmwork    1:06:15              1:07:47               2.31

                              kernel       5.57                    5.56                    -0.28

                              eSDK         3:02                    3:06                     2.20





ptest



There is an improvement of 2.1 % on the pass rate of glib-2.0 in 2.3.2 rc1 vs the pass rate in 2.3.1 rc2.  There is a regression of the pass rate of libxml2 and busybox of 4.2% and .1% respectively.



======= QA-Hints========



QA needs help from Joshua and the official AB so that we may run the Ubuntu 17.04 distro testing, if you have an Ubuntu 17.04 worker. With the objective that the report would be complete before CCB session finishes analyzing the results from this release.



QA finds 2.3.2 rc1 to be on the overall a stable release candidate.



======= Bugs ========



       New Bugs

            -12114[4]  oe-selftest on Ubuntu1704 hangs due to a resource warning of unclosed file



       M+ Bugs

            -11879[1]  Testimage: multiple "uvesafb" errors present in log in minnowmax on genericx86/genericx86-64

            -10455[2]  [morty][Test Case 1059] Parselogs is failing on genericx86 (32 and 64 bits) giving error: blk_update_request: I/O error, dev loop0

            -10477[3]  yocto-bsp: tool should output a conf file to be consume by the qemu runner



Full Bug Report : https://wiki.yoctoproject.org/wiki/WW38_-_2017-09-20-_Full_Test_Cycle_-_2.3.2_rc1





======== Links =========



    1.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=11879 [1]

    2.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=10455 [2]

    3.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=10477 [3]
    4.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12114 [4]







Regards

Libertad G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170921/1ab89e45/attachment.html>


More information about the yocto mailing list