[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ovmf baseline-only test] 68276: regressions - FAIL



This run is configured for baseline tests only.

flight 68276 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68276/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-ovmf-amd64 14 guest-saverestore.2 fail REGR. vs. 
68275

version targeted for testing:
 ovmf                 1f20b2988cb223907e64a4736a3eb6030aa715b8
baseline version:
 ovmf                 12b96a93f3f4f6827242f83f108a8d9c209dc6d0

Last test of basis    68275  2016-12-26 15:49:15 Z    0 days
Testing same since    68276  2016-12-26 19:16:00 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Star Zeng <star.zeng@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         fail    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit 1f20b2988cb223907e64a4736a3eb6030aa715b8
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Dec 16 18:07:43 2016 +0800

    IntelFrameworkModulePkg KbDxe: Execute key notify func at TPL_CALLBACK
    
    Current implementation executes key notify function in TimerHandler
    at TPL_NOTIFY. The code change is to make key notify function
    executed at TPL_CALLBACK to reduce the time occupied at TPL_NOTIFY.
    
    The code will signal KeyNotify process event if the key pressed
    matches any key registered and insert the KeyData to the EFI Key
    queue for notify, then the KeyNotify process handler will invoke
    key notify functions at TPL_CALLBACK.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

commit 7863d11c0092bbe6507c8bebbde6cb5784184657
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Dec 16 18:07:12 2016 +0800

    IntelFrameworkModulePkg Ps2KbDxe: Execute key notify func at TPL_CALLBACK
    
    Current implementation executes key notify function in TimerHandler
    at TPL_NOTIFY. The code change is to make key notify function
    executed at TPL_CALLBACK to reduce the time occupied at TPL_NOTIFY.
    
    The code will signal KeyNotify process event if the key pressed
    matches any key registered and insert the KeyData to the EFI Key
    queue for notify, then the KeyNotify process handler will invoke
    key notify functions at TPL_CALLBACK.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

commit 35dadd7c54ef12c87672c5eea35a75fa545ce68e
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Dec 16 18:08:18 2016 +0800

    MdeModulePkg Ps2KbDxe: Execute key notify func at TPL_CALLBACK
    
    Current implementation executes key notify function in TimerHandler
    at TPL_NOTIFY. The code change is to make key notify function
    executed at TPL_CALLBACK to reduce the time occupied at TPL_NOTIFY.
    
    The code will signal KeyNotify process event if the key pressed
    matches any key registered and insert the KeyData to the EFI Key
    queue for notify, then the KeyNotify process handler will invoke
    key notify functions at TPL_CALLBACK.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

commit 47b612db902fcdd133dc69b5db8d304f7498bd10
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Mon Dec 19 22:21:11 2016 +0800

    MdeModulePkg TerminalDxe: Execute key notify func at TPL_CALLBACK
    
    Current implementation executes key notify function in TimerHandler
    at TPL_NOTIFY. The code change is to make key notify function
    executed at TPL_CALLBACK to reduce the time occupied at TPL_NOTIFY.
    
    The code will signal KeyNotify process event if the key pressed
    matches any key registered and insert the KeyData to the EFI Key
    queue for notify, then the KeyNotify process handler will invoke
    key notify functions at TPL_CALLBACK.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

commit 4ae46dbacd8b049c66714c3578a88ecc09dcec95
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Dec 16 17:16:22 2016 +0800

    MdeModulePkg UsbKbDxe: Execute key notify func at TPL_CALLBACK
    
    Current implementation executes key notify function in TimerHandler
    at TPL_NOTIFY. The code change is to make key notify function
    executed at TPL_CALLBACK to reduce the time occupied at TPL_NOTIFY.
    
    The code will signal KeyNotify process event if the key pressed
    matches any key registered and insert the KeyData to the EFI Key
    queue for notify, then the KeyNotify process handler will invoke
    key notify functions at TPL_CALLBACK.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

commit cf88579c10f05554c25b1dd0318625f26d10097c
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Apr 15 17:38:51 2016 +0800

    MdeModulePkg ConSplitterDxe: Support toggle state sync
    
    Register key notify for toggle state (CapsLock, NumLock and ScrollLock)
    sync between multiple keyboards.
    The implementation for this feature requires keyboard driver supports
    EFI_KEY_STATE_EXPOSED, and turns on physical TextInEx partial key
    report for toggle state sync.
    The virtual TextInEx will report the partial key after it is required
    by calling SetState(X | KEY_STATE_VALID_EXPOSED) explicitly.
    
    Cc: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx>

_______________________________________________
osstest-output mailing list
osstest-output@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.