From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org, Jan Beulich <JBeulich@suse.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [xen-unstable-smoke bisection] complete build-amd64
Date: Sat, 13 Apr 2019 16:53:29 +0100 [thread overview]
Message-ID: <d84efa51-97d6-9b15-1434-43c16da5792a@citrix.com> (raw)
In-Reply-To: <fca33f27-821b-cc5e-3ed7-b760fc4219dd@arm.com>
On 13/04/2019 16:51, Julien Grall wrote:
> Hi,
>
> It looks like the amd64 build is broken on staging:
>
> http://logs.test-lab.xenproject.org/osstest/logs/134748/build-amd64/6.ts-xen-build.log
Yes it is. There is currently a patch out on xen-devel.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
osstest service owner <osstest-admin@xenproject.org>,
<xen-devel@lists.xenproject.org>, Jan Beulich <JBeulich@suse.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [Xen-devel] [xen-unstable-smoke bisection] complete build-amd64
Date: Sat, 13 Apr 2019 16:53:29 +0100 [thread overview]
Message-ID: <d84efa51-97d6-9b15-1434-43c16da5792a@citrix.com> (raw)
Message-ID: <20190413155329.u2tWQb-9-TnGuoQWl1SeMfA77VWyd6htD5uK-dtUll8@z> (raw)
In-Reply-To: <fca33f27-821b-cc5e-3ed7-b760fc4219dd@arm.com>
On 13/04/2019 16:51, Julien Grall wrote:
> Hi,
>
> It looks like the amd64 build is broken on staging:
>
> http://logs.test-lab.xenproject.org/osstest/logs/134748/build-amd64/6.ts-xen-build.log
Yes it is. There is currently a patch out on xen-devel.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-13 15:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 5:09 [xen-unstable-smoke bisection] complete build-amd64 osstest service owner
2019-04-13 5:09 ` [Xen-devel] " osstest service owner
2019-04-13 15:51 ` Julien Grall
2019-04-13 15:51 ` [Xen-devel] " Julien Grall
2019-04-13 15:53 ` Andrew Cooper [this message]
2019-04-13 15:53 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 17:02 osstest service owner
2023-09-06 16:46 osstest service owner
2023-06-07 16:24 osstest service owner
2023-03-24 22:28 osstest service owner
2022-10-16 8:24 osstest service owner
2022-03-15 2:25 osstest service owner
2022-01-21 3:38 osstest service owner
2022-01-21 7:54 ` Jan Beulich
2021-08-16 23:23 osstest service owner
2021-07-10 0:19 osstest service owner
2021-07-06 17:29 osstest service owner
2021-02-24 16:57 osstest service owner
2021-02-10 19:10 osstest service owner
2021-01-28 18:38 osstest service owner
2020-12-21 20:07 osstest service owner
2020-11-10 23:25 osstest service owner
2020-10-23 23:30 osstest service owner
2020-10-07 18:40 osstest service owner
2020-04-25 8:57 osstest service owner
2019-05-15 8:13 osstest service owner
2019-01-02 21:14 osstest service owner
2018-11-12 23:38 osstest service owner
2018-09-25 21:39 osstest service owner
2018-04-07 6:19 osstest service owner
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=d84efa51-97d6-9b15-1434-43c16da5792a@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=julien.grall@arm.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 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).