xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 74752: all pass
Date: Mon, 28 May 2018 14:55:53 +0100	[thread overview]
Message-ID: <osstest-74752-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 03ac238b1fe40cfbb1424bf72e2ac8276345e03c
baseline version:
 ovmf                 7dc7c7435e9030ad07ad7bc7d136a3997bd0b182

Last test of basis    74748  2018-05-26 04:52:45 Z    2 days
Testing same since    74752  2018-05-27 06:20:53 Z    1 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@intel.com>

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                         pass    
 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 03ac238b1fe40cfbb1424bf72e2ac8276345e03c
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Wed May 23 11:28:46 2018 +0800

    MdeModulePkg/PciBus: Use actual max bus # for subordinary bus #
    
    Current code assumes the max bus(0xFF) is under this P2P bridge and
    temporarily set it as subordinate bus.
    It may cause silicon hangs during PCI enumeration in some specific
    case.
    
    Instead, it should get the max bus number from the bus number
    resources returned from
    PCI_HOST_BRIDGE_RESOURCE_ALLOCATION.StartBusEnumeration() and set it
    as subordinate bus.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Star Zeng <star.zeng@intel.com>

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

                 reply	other threads:[~2018-05-28 13:55 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-74752-mainreport@xen.org \
    --to=citrix-osstest@xenproject.org \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).