From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 159125: trouble: preparing/queued/running
Date: Mon, 08 Feb 2021 10:46:19 +0000 [thread overview]
Message-ID: <osstest-159125-mainreport@xen.org> (raw)
flight 159125 ovmf running [real]
http://logs.test-lab.xenproject.org/osstest/logs/159125/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386 4 host-install(4) broken REGR. vs. 159040
build-amd64-libvirt <none executed> queued
build-i386-libvirt <none executed> queued
test-amd64-amd64-xl-qemuu-ovmf-amd64 <none executed> queued
test-amd64-i386-xl-qemuu-ovmf-amd64 <none executed> queued
build-i386-xsm 2 hosts-allocate running
build-amd64-xsm 2 hosts-allocate running
build-i386-pvops 2 hosts-allocate running
build-amd64 2 hosts-allocate running
build-amd64-pvops 2 hosts-allocate running
build-i386 3 syslog-server running
version targeted for testing:
ovmf 43a113385e370530eb52cf2e55b3019d8d4f6558
baseline version:
ovmf 0d96664df322d50e0ac54130e129c0bf4f2b72df
Last test of basis 159040 2021-02-05 11:11:01 Z 2 days
Testing same since 159088 2021-02-07 01:54:46 Z 1 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Bob Feng <bob.c.feng@intel.com>
Liming Gao <gaoliming@byosoft.com.cn>
jobs:
build-amd64-xsm preparing
build-i386-xsm preparing
build-amd64 preparing
build-i386 running
build-amd64-libvirt queued
build-i386-libvirt queued
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.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-job build-amd64-libvirt queued
broken-job build-i386-libvirt queued
broken-job test-amd64-amd64-xl-qemuu-ovmf-amd64 queued
broken-job test-amd64-i386-xl-qemuu-ovmf-amd64 queued
broken-step build-i386 host-install(4)
Not pushing.
------------------------------------------------------------
commit 43a113385e370530eb52cf2e55b3019d8d4f6558
Author: Bob Feng <bob.c.feng@intel.com>
Date: Mon Feb 1 18:28:58 2021 +0800
BaseTools: fix the split output files root dir
If the output file path is a relative path, the split
tool will create the output file under the input file path.
But the expected behavior for this case is the output file
should be relative to the current directory. This patch will
fix this bug.
If the output file path is not specified and output prefix is not
specified, the output file should be under the input file path
Signed-off-by: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Acked-by: Liming Gao <gaoliming@byosoft.com.cn>
Reviewed-by: Yuwei Chen <yuwei.chen@intel.com>
reply other threads:[~2021-02-08 10:46 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-159125-mainreport@xen.org \
--to=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 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.