Bug 12075

Summary: [morty] testimage quemux86/qemux86-64 lsb tcgetattr: Input/output error^M
Product: [Build System, Metadata & Runtime] BSPs Reporter: Juan Ramos <juan.fernandox.ramos.frayle>
Component: bsps-configurationAssignee: Armin Kuster <akuster>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Medium+ CC: richard.purdie, yp.bsp.watcher, yp.watcher
Version: 2.2   
Target Milestone: 2.2.3   
Hardware: Other   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
testimage_qemux86.log
none
testimage_qemux86-64.log none

Description Juan Ramos 2017-09-13 00:32:31 UTC 
Created attachment 4003 [details]
testimage_qemux86.log

STATUS: IDLE
BUILD: 2.2.2: rc2-60402978fe3648bf560b3386c6e9dd661cdf2083
ENVIRONMENT: qemux86-lsb
Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky-lsb"
DISTRO_VERSION    = "2.2.2"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "HEAD:60402978fe3648bf560b3386c6e9dd661cdf2083"

STEPS TO REPRODUCE: 
1. Get the images needed to run automated qemux86 LSB test from:
https://autobuilder.yocto.io/pub/releases/yocto-2.2.2.rc2/machines/qemu/qemux86-lsb/
2. Clone poky and configure to run automated qemux86 LSB test like this:
https://wiki.yoctoproject.org/wiki/Additional_Steps_for_Automated_Testing_on_QEMU

3. $bitbake core-image-lsb-sdk -c testimage


EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:

AssertionError: 50 != 0 
-----------------------
Central error: Sep 11 22:55:42 qemux86 getty[12494]: tcgetattr: Input/output error^M 

NOTE: As said in bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11598
this can be backported once merged into master/pyro/...
and already merge into latest master, but I guess this didn't backported, it still present.
NOTE 2: This is present in both qemux86 and quemux86-64.
Log attached.
Comment 1 Juan Ramos 2017-09-13 16:29:42 UTC 
Created attachment 4006 [details]
testimage_qemux86-64.log
Comment 2 Armin Kuster 2017-11-10 16:50:17 UTC 
wow.. the fix is between 573c646d4cc62dcd0c230381df4940bdf314d495..415b72ffcbd26e5f3664370d8b2a9b8105fb6342

with no commit referenced as fixing the issue. nice
Comment 3 Armin Kuster 2017-11-10 22:55:06 UTC 
can not reproduce this with current akuster/morty-next.
since no specific commit was identified, its hard to know if I have already included the fix.
Comment 4 Armin Kuster 2017-11-21 15:44:32 UTC 
do not see this issue in AB in the last few build.
Comment 5 Richard Purdie 2018-01-04 15:57:30 UTC 
We've not seen this in many builds. Closing, reopen if we see it again.