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] 68162: all pass
Date: Mon, 5 Dec 2016 19:55:14 +0000	[thread overview]
Message-ID: <osstest-68162-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 0db4acb61ac4e79a8a95b0e82874e8b6bed8e4bb
baseline version:
 ovmf                 7bbe0b3eff9e7876808ce1b96b9a71360984cf91

Last test of basis    68154  2016-12-04 02:17:11 Z    1 days
Testing same since    68162  2016-12-05 17:21:10 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chen A Chen <chen.a.chen@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 0db4acb61ac4e79a8a95b0e82874e8b6bed8e4bb
Author: Chen A Chen <chen.a.chen@intel.com>
Date:   Tue Nov 22 16:16:02 2016 +0800

    ShellPkg/MV: Fix MV to deny moving parent of current directory
    
    When user types "mv -r fs0:\A\ fs1:\" under directory
    "fs0:\A\B\", MV command should deny such movement.
    
    The patch fixes the above issue.
    It also denies moving current directory.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Chen A Chen <chen.a.chen@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>

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

                 reply	other threads:[~2016-12-05 19: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-68162-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).