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.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 72016: all pass
Date: Fri, 25 Aug 2017 10:48:50 +0100	[thread overview]
Message-ID: <osstest-72016-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 279c01ce13739f0fd8ec3e7652299f6873fc14a9
baseline version:
 ovmf                 e4d409c6e3b96738fb0c710ecd21bcd79db93381

Last test of basis    72012  2017-08-24 07:48:04 Z    1 days
Testing same since    72016  2017-08-25 05:24:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Liming Gao <liming.gao@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 279c01ce13739f0fd8ec3e7652299f6873fc14a9
Author: Liming Gao <liming.gao@intel.com>
Date:   Tue Aug 22 13:58:57 2017 +0800

    BaseTools: Roll back GenFw Change to keep unknown field in RSDS debug entry
    
    https://lists.01.org/pipermail/edk2-devel/2017-August/013488.html
    These fields are actually a GUID and DWORD respectively: the GUID identifies
    the PDB to make it possible to verify that a given PDB matches the PE file,
    and the DWORD is the "age" of the PDB which is simply a helper value that is
    incremented by 1 by the linker every time the file is remade. Wiping the
    GUID will cause PDB parsers (such as the MS DIA SDK that IDA and most other
    tools use) to treat the PDB as a mismatch and refuse to load it.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Liming Gao <liming.gao@intel.com>

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

                 reply	other threads:[~2017-08-25  9:48 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-72016-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 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).