From: "Roger Pau Monné" <royger@FreeBSD.org>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [freebsd-master test] 124935: trouble: blocked/broken
Date: Wed, 4 Jul 2018 08:49:28 +0200 [thread overview]
Message-ID: <20180704064928.lwg6brh5ntr4ypxv@mac.bytemobile.com> (raw)
In-Reply-To: <osstest-124935-mainreport@xen.org>
On Wed, Jul 04, 2018 at 02:52:05AM +0000, osstest service owner wrote:
> flight 124935 freebsd-master real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/124935/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-amd64-freebsd <job status> broken
> build-amd64-freebsd 5 host-install(5) broken REGR. vs. 124909
This failure is caused because the host is set to boot from UEFI, and
there's no logic yet in osstest to install FreeBSD from UEFI.
Is there anyway to prevent the FreeBSD jobs from running in
albana{0|1} (or UEFI boxes in general)?
Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-04 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 2:52 [freebsd-master test] 124935: trouble: blocked/broken osstest service owner
2018-07-04 6:49 ` Roger Pau Monné [this message]
2018-07-04 10:55 ` Ian Jackson
2018-07-04 10:56 ` [OSSTEST PATCH 1/3] resource allocation: PropCompareBase: Break out _get_val Ian Jackson
2018-07-04 10:56 ` [OSSTEST PATCH 2/3] resource allocation: PropEq, PropMinVer: Honour HostProp_ Ian Jackson
2018-07-04 10:56 ` [OSSTEST PATCH 3/3] resource allocation: PropEq, PropMinVer: support defaults Ian Jackson
2018-07-04 10:59 ` [freebsd-master test] 124935: trouble: blocked/broken Ian Jackson
2018-07-04 11:21 ` Roger Pau Monné
2018-07-04 10:30 ` Ian Jackson
2018-07-04 10:48 ` Roger Pau Monné
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=20180704064928.lwg6brh5ntr4ypxv@mac.bytemobile.com \
--to=royger@freebsd.org \
--cc=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.