From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 107202: regressions - trouble: broken/fail/pass
Date: Tue, 04 Apr 2017 22:35:13 +0000 [thread overview]
Message-ID: <osstest-107202-mainreport@xen.org> (raw)
flight 107202 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107202/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 107194
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
build-arm64-pvops 5 kernel-build fail never pass
version targeted for testing:
xen 045d5d10ee5f0066a7e71d1fe18f9c7c27d64703
baseline version:
xen c4bdbec00c9063736361124a3492ebceabfaed06
Last test of basis 107194 2017-04-04 16:01:54 Z 0 days
Testing same since 107202 2017-04-04 21:17:38 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Oleksandr Grytsov <oleksandr_grytsov@epam.com>
jobs:
build-amd64 pass
build-armhf pass
build-amd64-libvirt pass
build-arm64-pvops fail
test-armhf-armhf-xl fail
test-arm64-arm64-xl-xsm broken
test-amd64-amd64-xl-qemuu-debianhvm-i386 pass
test-amd64-amd64-libvirt pass
------------------------------------------------------------
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
Not pushing.
------------------------------------------------------------
commit 045d5d10ee5f0066a7e71d1fe18f9c7c27d64703
Author: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Date: Mon Mar 20 09:03:27 2017 +0200
xen/sndif: Add sound-device ABI
Add ABI for the two halves of a para-virtualized
sound driver to communicate with each other.
The ABI allows implementing audio playback and capture as
well as volume control and possibility to mute/unmute
audio sources.
Note: depending on the use-case backend can expose more sound
cards and PCM devices/streams than the underlying HW physically
has by employing SW mixers, configuring virtual sound streams,
channels etc. Thus, allowing fine tunned configurations per
frontend.
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Signed-off-by: Oleksandr Grytsov <oleksandr_grytsov@epam.com>
Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Signed-off-by: Iurii Konovalenko <iurii.konovalenko@globallogic.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-04-04 22:35 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-107202-mainreport@xen.org \
--to=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).