flight 139670 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139670/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 10 xen-boot/src_hostfail REGR. vs. 139649
flight 139669 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139669/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-raw7 xen-boot fail REGR. vs. 133580
Hi,
Sorry for the late reply.
> I have seen multiple threads from you pointing at issues on the IMX.8. Have
> they
> been resolved? Is this series enough to get Xen and Dom0 booting on the NXP
> platform?
Yeah, most of issues are resolved now and mainline DTS is used to
bring XEN on this i.MX8
On 8/2/19 11:48 AM, John Hubbard wrote:
> On 8/2/19 2:19 AM, Joonas Lahtinen wrote:
>> Quoting john.hubb...@gmail.com (2019-08-02 05:19:37)
>>> From: John Hubbard
...
> In order to deal with the merge problem, I'll drop this patch from my series,
> and I'd recommend that the drm-intel-next take
flight 139675 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139675/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl
flight 139659 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139659/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 12 guest-start fail REGR. vs. 139633
Tests which did
On 31/07/2019 17:58, Dario Faggioli wrote:
> The openSUSE distribution comes in two flavours: Leap, which is
> non-rolling, and released annualy, and Tumbleweed, which is rolling.
>
> In general, they are quite similar, but the versions of the software
> they ship can be significantly different.
flight 139655 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139655/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 6 kernel-build fail REGR. vs. 129313
Tests which are
flight 139663 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139663/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 139627
test-armhf-armhf-libvirt-raw 13
flight 139666 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139666/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf afebc51547082faa080b3a5e7d5cb2e5a3cd1532
baseline version:
ovmf
On 7/31/19 11:58 AM, Dario Faggioli wrote:
openSUSE comes in two flavours: Leap, which is non-rolling, and released
annualy, and Tumbleweed, which is rolling.
Reasons why it makes sense to have both (despite both being openSUSE,
package lists in dockerfiles being quite similar, etc) are:
-
On 7/31/19 11:58 AM, Dario Faggioli wrote:
Signed-off-by: Dario Faggioli
Acked-by: Doug Goldstein
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 7/31/19 11:58 AM, Dario Faggioli wrote:
Using `--no-recommends` when updating or installing commands should
prevent non strictly necessary packages to be installed.
doing a `clean -a` after installing all the packages, should, in
theory, free more space (as opposed to using just `clean`).
To be able to push a container, users must have access and have logged
into the container registry. The docs did not explain this fully so this
documents the steps better.
Signed-off-by: Doug Goldstein
---
automation/build/README.md | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
On 8/2/19 9:37 AM, Dario Faggioli wrote:
On Fri, 2019-08-02 at 13:11 +0100, Andrew Cooper wrote:
On 02/08/2019 13:00, Dario Faggioli wrote:
On Mon, 2019-07-29 at 12:18 -0500, Doug Goldstein wrote:
Will you be pushing the rebuilt container or do you need me to do
that?
So, I guess someone
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-libvirt-pair
testid xen-boot/dst_host
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_gnulib https://git.savannah.gnu.org/git/gnulib.git/
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree:
flight 139649 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139649/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-qemuu-rhel6hvm-intel 12 guest-start/redhat.repeat fail in
139621 pass in 139649
flight 139642 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139642/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm broken
test-amd64-i386-xl-raw
flight 139653 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139653/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 89164babecceb03047c4aec8e76c4d838d703095
baseline version:
ovmf
On Thu, Aug 01, 2019 at 07:19:46PM -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide
On Thu, Aug 01, 2019 at 07:19:41PM -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide
21 matches
Mail list logo
