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

[ovmf baseline-only test] 75219: trouble: blocked/broken



This run is configured for baseline tests only.

flight 75219 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75219/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 build-amd64-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  1 build-check(1)             blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 build-i386                    4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested
 build-amd64                   4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 f316a26013f2a8cfb1041d9f74a5c6d5bb9df9c9
baseline version:
 ovmf                 52664c525223a36e5cb9b141b11dec413908b1dd

Last test of basis    75215  2018-09-13 15:19:33 Z    0 days
Testing same since    75219  2018-09-14 05:20:10 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Dandan Bi <dandan.bi@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              broken  
 build-i386-xsm                                               broken  
 build-amd64                                                  broken  
 build-i386                                                   broken  
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            broken  
 build-i386-pvops                                             broken  
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         blocked 
 test-amd64-i386-xl-qemuu-ovmf-amd64                          blocked 


------------------------------------------------------------
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.xensource.com/osstest/logs

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

broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64 host-install(4)

Push not applicable.

------------------------------------------------------------
commit f316a26013f2a8cfb1041d9f74a5c6d5bb9df9c9
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Sun Sep 9 22:34:57 2018 +0800

    MdeModulePkg: Avoid key notification called more than once
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=996
    
    Issue:
    In current code logic, when a key is pressed, it will search
    the whole NotifyList to find whether a notification has been
    registered with the keystroke. if yes, it will en-queue the
    key for notification execution later. And now if different
    notification functions have been registered with the same key,
    then the key will be en-queued more than once. Then it will
    cause the notification executed more than once.
    
    This patch is to enhance the code logic to fix this issue.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit f92b8ee3b7a621d0db8708ec05ee13639436b4a9
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Sun Sep 9 22:29:56 2018 +0800

    IntelFrameworkModulePkg: Avoid key notification called more than once
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=996
    
    Issue:
    In current code logic, when a key is pressed, it will search
    the whole NotifyList to find whether a notification has been
    registered with the keystroke. if yes, it will en-queue the
    key for notification execution later. And now if different
    notification functions have been registered with the same key,
    then the key will be en-queued more than once. Then it will
    cause the notification executed more than once.
    
    This patch is to enhance the code logic to fix this issue.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

commit 9c8e9e76bd06014e430ecfa6c8f8e21374005a29
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Sun Sep 9 22:26:07 2018 +0800

    EmbeddedPkg/VirtualKeyboard: Avoid notification called more than once
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=996
    
    Issue:
    In current code logic, when a key is pressed, it will search
    the whole NotifyList to find whether a notification has been
    registered with the keystroke. if yes, it will en-queue the
    key for notification execution later. And now if different
    notification functions have been registered with the same key,
    then the key will be en-queued more than once. Then it will
    cause the notification executed more than once.
    
    This patch is to enhance the code logic to fix this issue.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Leif Lindholm <leif.lindholm@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

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

 


Rackspace

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