From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [seabios baseline-only test] 68604: tolerable FAIL
Date: Thu, 23 Feb 2017 02:34:39 +0000 [thread overview]
Message-ID: <osstest-68604-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 68604 seabios real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68604/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 68585
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 68585
test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail like 68585
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 9 windows-install fail like 68585
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass
version targeted for testing:
seabios 8f598a4641f98cf503653f80c779793d91c95a84
baseline version:
seabios c83e15b60b7c59552a44d71d0582f2d62a6084a7
Last test of basis 68585 2017-02-21 01:19:55 Z 2 days
Testing same since 68604 2017-02-22 20:19:52 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ben Warren <ben@skyportsystems.com>
Kevin O'Connor <kevin@koconnor.net>
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-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-qemuu-nested-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-amd64-xl-qemuu-winxpsp3 pass
test-amd64-i386-xl-qemuu-winxpsp3 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 8f598a4641f98cf503653f80c779793d91c95a84
Author: Ben Warren <ben@skyportsystems.com>
Date: Mon Feb 20 19:56:19 2017 -0800
QEMU fw_cfg: Write fw_cfg back on S3 resume
Any pointers to BIOS-allocated memory that were written back to QEMU
fw_cfg files are replayed when resuming from S3 sleep.
Signed-off-by: Ben Warren <ben@skyportsystems.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
commit 336b60bb10196adf287489cca4fd17092d9fac5e
Author: Ben Warren <ben@skyportsystems.com>
Date: Mon Feb 20 19:56:18 2017 -0800
QEMU fw_cfg: Add functions for accessing files by key
Due to memory contraints, when resuming from S3 the fw_cfg "files" API
isn't available. This adds a simple API to get a file 'key', and to
write to the file using the key as a reference.
Signed-off-by: Ben Warren <ben@skyportsystems.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
commit bb9cbbcabc37665cb645cacd1cfefbfe1f4364ab
Author: Ben Warren <ben@skyportsystems.com>
Date: Mon Feb 20 19:56:17 2017 -0800
QEMU fw_cfg: Add command to write back address of file
This command is similar to ADD_POINTER, but instead of patching
memory, it writes the pointer back to QEMU over the DMA interface.
Signed-off-by: Ben Warren <ben@skyportsystems.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
commit e5bebc77d2a9dfa67cda100b67d787c3ebdb5397
Author: Ben Warren <ben@skyportsystems.com>
Date: Mon Feb 20 19:56:16 2017 -0800
romfile-loader: Switch to using named structs
This is a little cleaner and matches how the command structures are
defined in QEMU.
Signed-off-by: Ben Warren <ben@skyportsystems.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
commit f991822f24adbeea519495dd8fe2d8ca7ed47291
Author: Ben Warren <ben@skyportsystems.com>
Date: Mon Feb 20 19:56:15 2017 -0800
QEMU DMA: Add DMA write capability
This allows BIOS to write data back to QEMU using the DMA interface and
provides a higher-level abstraction to write to a fw_cfg file
Signed-off-by: Ben Warren <ben@skyportsystems.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-02-23 2:34 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-68604-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.