Bug 8889

Summary: test_systemd_boot_time sometimes fails due to "invalid literal for float()"
Product: [QA/Testing] Manual Testing Reporter: Randy Witt <randy.e.witt>
Component: manual-testingAssignee: Benjamin Esquivel <benjamin.esquivel>
Status: VERIFIED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu, benjamin.esquivel, leonardo.sandoval.gonzalez
Version: 2.0   
Target Milestone: 2.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Full testimage log as requested.
none
Verified Bug Passed none

Description Randy Witt 2016-01-06 19:01:42 UTC
Using committish 2cd061a29a94fdcdfec86732e6bcbb71c12c4afc and running the systemd tests using "-c testimage" I saw the failure below 67 times out of ~4700 runs.

| test_systemd_stop_start (oeqa.runtime.systemd.SystemdServiceTests) ... ok     
|                                                                               
| ======================================================================        
| ERROR: test_systemd_boot_time (oeqa.runtime.systemd.SystemdJournalTests)      
| ----------------------------------------------------------------------        
| Traceback (most recent call last):                                            
|   File "/home/yoctouser/copied_pokydir/meta/lib/oeqa/utils/decorators.py", line 94, in wrapped_f
|     return f(*args, **kwargs)                                                 
|   File "/home/yoctouser/copied_pokydir/meta/lib/oeqa/runtime/systemd.py", line 172, in test_systemd_boot_time
|     boot_time_sec += float(l_boot_time[1].split("s")[0])                      
| ValueError: invalid literal for float(): 11m
Comment 1 Benjamin Esquivel 2016-01-07 15:58:22 UTC
Is it possible for you to attach the full log of the testing? I want to see the original string it is trying to parse. This is a very interesting case
Comment 2 Randy Witt 2016-01-11 20:19:57 UTC
(In reply to comment #1)
> Is it possible for you to attach the full log of the testing? I want to see
> the original string it is trying to parse. This is a very interesting case

I don't have them anymore.(I'm not sure why I deleted them) I'll try to reproduce.
Comment 3 Randy Witt 2016-01-11 21:05:17 UTC
Created attachment 2926 [details]
Full testimage log as requested.
Comment 4 Benjamin Esquivel 2016-02-01 06:24:44 UTC
the first approach will be to add a try statement to catch this exception and handle properly.
Comment 5 Benjamin Esquivel 2016-02-01 12:09:27 UTC
sent to the list:

http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116567.html
Comment 7 Francisco Pedraza 2016-03-10 15:49:06 UTC
Created attachment 3022 [details]
Verified Bug Passed

Verification, working fine.

Build Configuration:
BB_VERSION        = "1.29.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-22"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.0+snapshot-20160310"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-yocto
meta-yocto-bsp    = "HEAD:637b44ce7c82c3bf4756f087559330e531cc12d1"
Comment 8 Francisco Pedraza 2016-03-10 15:51:01 UTC
Verified Bug Passed

Verification, working fine.

Build Configuration:
BB_VERSION        = "1.29.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-22"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.0+snapshot-20160310"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-yocto
meta-yocto-bsp    = "HEAD:637b44ce7c82c3bf4756f087559330e531cc12d1"
Comment 9 Benjamin Esquivel 2016-03-22 21:55:13 UTC
Hey Francisco, you took this bug as yours when you should have only taken the verification of it. Saludos.