Bug 12127 - Duplicate log observed on oe-selftest runs
Summary: Duplicate log observed on oe-selftest runs
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M1
Assignee: Jair Gonzalez
QA Contact:
URL:
Whiteboard:
: 12257 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-09-26 13:47 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-11-09 13:27 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

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo Sandoval Gonzalez 2017-09-26 13:47:26 UTC
In recent runs, oe-selftest log have duplicate lines as observed in [1]:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/546/steps/Running%20oe-selftest/logs/stdio
Comment 1 Richard Purdie 2017-09-26 14:18:12 UTC
They seem to come from runqemu and for each runqemu run, a new level of duplication is added. This happens sometimes and not others, generally on newer autobuilders but doesn't always happen.
Comment 2 Ross Burton 2017-10-20 14:37:19 UTC
*** Bug 12257 has been marked as a duplicate of this bug. ***
Comment 3 Richard Purdie 2017-11-07 17:50:55 UTC
Starting to suspect this happens when there is a server reconnection. Each reconnection adds extra log duplication.
Comment 4 Aníbal Limón 2017-11-07 18:00:26 UTC
(In reply to comment #3)
> Starting to suspect this happens when there is a server reconnection. Each
> reconnection adds extra log duplication.

The qemu runner adds a new stream handler [1] when is lunched, the testimage class uses the main logger [2] and the oe-selftest script also initialize its own logger [3].

For me the qemu runner needs to use the logger from outside (testimage, selftest), instead of add every time an StreamHandler [3] that cuases the duplication. [4]



[1]  http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/utils/qemurunner.py#n60
[2] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/testimage.bbclass#n160
[3] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/oe-selftest#n46
[4] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/utils/commands.py#n331
Comment 5 Richard Purdie 2017-11-09 13:27:22 UTC
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a87cae5bb1b0168b29eef7076756ef1d7179ee72 and the preceding 8 commits address this issue. Appears that a python bug was fixed in 3.6 which started exposing these messages.

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=729b1d3afd3d4b8eed4a4f4ddeb27780db47dcd5 in particular.