All of lore.kernel.org
 help / color / mirror / Atom feed
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 74529: trouble: blocked/broken/preparing/queued
Date: Fri, 6 Apr 2018 11:54:46 +0100	[thread overview]
Message-ID: <osstest-74529-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-xsm                  <job status>                 broken
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 test-amd64-i386-xl-qemuu-ovmf-amd64    <none executed>              queued
 build-amd64-libvirt             <none executed>              queued
 test-amd64-amd64-xl-qemuu-ovmf-amd64    <none executed>              queued
 build-amd64-pvops             2 hosts-allocate               running
 build-amd64                   2 hosts-allocate               running
 build-i386-pvops              2 hosts-allocate               running

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

version targeted for testing:
 ovmf                 aae02dccf5b0ad07e60d2738f350b3b39df389d7
baseline version:
 ovmf                 c4172f80051effc62f3eceeeced4c0b66a80eb94

Last test of basis    74496  2018-04-05 12:23:44 Z    0 days
Testing same since                          (not found)         0 attempts

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

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


------------------------------------------------------------
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

broken-job test-amd64-i386-xl-qemuu-ovmf-amd64 queued
broken-job build-amd64-libvirt queued
broken-job build-i386-xsm broken
broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job test-amd64-amd64-xl-qemuu-ovmf-amd64 queued
broken-step build-amd64-xsm host-install(4)
broken-step build-i386 host-install(4)
broken-step build-i386-xsm host-install(4)

Push not applicable.

------------------------------------------------------------
commit aae02dccf5b0ad07e60d2738f350b3b39df389d7
Author: Star Zeng <star.zeng@intel.com>
Date:   Wed Feb 28 13:21:59 2018 +0800

    UefiCpuPkg PiSmmCpuDxeSmm: Refine some comments about SmmMemoryAttribute
    
    1. Fix some "support" to "supported".
    2. Fix some "set" to "clear" in ClearMemoryAttributes interface.
    3. Remove redundant comments for GetMemoryAttributes interface.
    
    Cc: Jian J Wang <jian.j.wang@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Eric Dong <eric.dong@intel.com>
    Cc: Laszlo Ersek <lersek@redhat.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Jian J Wang <jian.j.wang@intel.com>
    Reviewed-by: Laszlo Ersek <lersek@redhat.com>

commit 5942b32e798f7e49c9c5c2ef10f4ac2ad0647598
Author: Star Zeng <star.zeng@intel.com>
Date:   Wed Feb 28 13:20:34 2018 +0800

    MdeModulePkg SmmMemoryAttribute.h: Refine some comments
    
    1. Fix some "support" to "supported".
    2. Fix some "set" to "clear" in ClearMemoryAttributes interface.
    3. Remove redundant comments for GetMemoryAttributes interface.
    
    Cc: Jian J Wang <jian.j.wang@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Jian J Wang <jian.j.wang@intel.com>
    Reviewed-by: Laszlo Ersek <lersek@redhat.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

                 reply	other threads:[~2018-04-06 10:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=osstest-74529-mainreport@xen.org \
    --to=citrix-osstest@xenproject.org \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.