From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Costin Lupu <costin.lupu@cs.pub.ro>
Cc: Jan Beulich <jbeulich@suse.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [xen-unstable-smoke test] 152898: regressions - FAIL
Date: Thu, 27 Aug 2020 20:38:03 +0200 [thread overview]
Message-ID: <20200827183803.32e5flm6dh62c3da@function> (raw)
In-Reply-To: <ef1ffb57-5d70-e819-f4cf-4ff632325b76@cs.pub.ro>
Costin Lupu, le jeu. 27 août 2020 19:47:08 +0300, a ecrit:
> On 8/27/20 7:07 PM, Jan Beulich wrote:
> > On 27.08.2020 17:49, osstest service owner wrote:
> >> flight 152898 xen-unstable-smoke real [real]
> >> http://logs.test-lab.xenproject.org/osstest/logs/152898/
> >>
> >> Regressions :-(
> >>
> >> Tests which did not succeed and are blocking,
> >> including tests which could not be run:
> >> build-amd64 6 xen-build fail REGR. vs. 152892
> >
> > This looks to be an issue in the mini-os tree, and I'm having
> > trouble understanding how it can cause the main tree to first
> > discover it. Is there no push gate for that tree?
> >
> > In any event, commit 1b8ed31f4ce4 ("mini-os: netfront: Read netmask
> > and gateway from Xenstore") looks to have missed callers to
> > init_netfront(), both in the mini-os tree itself and in stubdom/grub/
> > of the main tree.
>
> Hi Jan,
>
> Sorry for missing that. I've just sent a patch on the mini-os mailing
> list. Please let me know if it needs anything else.
We need a patch for stubdom/grub/mini-os.c
Samuel
prev parent reply other threads:[~2020-08-27 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 15:49 [xen-unstable-smoke test] 152898: regressions - FAIL osstest service owner
2020-08-27 16:07 ` Jan Beulich
2020-08-27 16:47 ` Costin Lupu
2020-08-27 18:38 ` Samuel Thibault [this message]
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=20200827183803.32e5flm6dh62c3da@function \
--to=samuel.thibault@ens-lyon.org \
--cc=costin.lupu@cs.pub.ro \
--cc=jbeulich@suse.com \
--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.