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] 68049: all pass
Date: Wed, 16 Nov 2016 12:53:00 +0000	[thread overview]
Message-ID: <osstest-68049-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 2adf689cb7c66f4790a7d0a9e7e99aad6ebee638
baseline version:
 ovmf                 86a1eca2101686d476ab191f0511b44e369fd8a7

Last test of basis    68046  2016-11-16 03:49:21 Z    0 days
Testing same since    68049  2016-11-16 08:19:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chen A Chen <chen.a.chen@intel.com>
  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 2adf689cb7c66f4790a7d0a9e7e99aad6ebee638
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Tue Nov 15 09:57:03 2016 +0800

    ShellPkg: #ifndef of header files should have postfix underscore
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Dandan Bi <dandan.bi@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>

commit e9597b4519cbeda1c5175518f79a80d7f0b6353b
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Fri Nov 11 12:12:51 2016 +0800

    ShellPkg/dmpstore: Support "-sfo"
    
    The patch adds the "-sfo" support to "dmpstore" command.
    
    When -l or -d is specified, -sfo is not supported.
    
    When the variable specified by name and GUID cannot be found,
    an error message is displayed; Otherwise, the SFO is displayed.
    E.g.: "dmpstore -guid GuidThatDoesntExist -sfo" produces output
    as:
    ShellCommand,"dmpstore"
    VariableInfo,"","GuidThatDoesntExist","","",""
    
    "dmpstore NameThatDoesntExist -guid GuidThatDoesntExist -sfo"
    produces output as:
    ShellCommand,"dmpstore"
    dmpstore: No matching variables found. Guid GuidThatDoesntExist, Name
    NameThatDoesntExist
    
    The difference between the above 2 cases is that former one only
    specifies the GUID, but the latter one specifies both name and GUID.
    Since not specifying GUID means to use GlobalVariableGuid,
    "dmpstore NameThatDoesntExist -sfo" produces the similar output as
    latter one.
    I personally prefer to always produce SFO output for both cases.
    But the above behavior is the discussion result between HPE engineers.
    
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Signed-off-by: Chen A Chen <chen.a.chen@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
    Reviewed-by: Tapan Shah <tapandshah@hpe.com>

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

                 reply	other threads:[~2016-11-16 12:53 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-68049-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.