From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: David Scott <dave@recoil.org>, Wei Liu <wei.liu2@citrix.com>,
Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
Date: Mon, 31 Oct 2016 10:37:35 +0000 [thread overview]
Message-ID: <3eae69fe-f8ba-a159-8948-b0f75a942f45@citrix.com> (raw)
In-Reply-To: <22551.7525.827545.264780@mariner.uk.xensource.com>
On 31/10/16 10:31, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [Xen-devel] [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm"):
>> On 30/10/16 04:29, osstest service owner wrote:
>>> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/101803/
> ...
>> Where can I find the build logs for the bisection runs? I am fairly
>> sure I have a newer version of Ocaml than comes by default in Debian,
>> and I wonder whether I have hit some version-dependent behaviour.
> Let me walk you through this.
>
> We'll follow links starting with, say, the "Last fail repro" url,
> above:
>
> http://logs.test-lab.xenproject.org/osstest/logs/101803/
>
> Click on the test column heading to get to
>
> http://logs.test-lab.xenproject.org/osstest/logs/101803/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/info.html
>
> Scroll down and you'll see `Test control variables'. Select the build
> of interest, which I think is `buildjob'. (There are also
> `xenbuildjob' which is the hypervisor build, and `kernbuildjob' which
> is, as might be expected, the kernel.) So click through to
> 101797.build-i386-xsm:
>
> http://logs.test-lab.xenproject.org/osstest/logs/101797/build-i386-xsm/info.html
>
> The main build log is that for the `xen-build' step:
>
> http://logs.test-lab.xenproject.org/osstest/logs/101797/build-i386-xsm/4.ts-xen-build-prep.log
>
> Finding out which ocaml was actually installed can sometimes be a
> little harder, because build host sharing means that the run of
> `host-build-prep' shown in that job might be a no-op, and there isn't
> an easy way to click through to the job that actually did the install
> (sorry).
>
> However, it's easy enough to know what ocaml was probably installed:
> looking at `Test control variables' in the build job, you see
> `all_host_suite' with value `jessie'. Then go here
>
> https://www.debian.org/distrib/packages
>
> and in the `search package directories' enter `ocaml' (searching
> within `stable', since jessie is currently stable);
>
> https://packages.debian.org/search?keywords=ocaml&searchon=names&suite=stable§ion=all
>
> Results: 4.01.0-5.
Thankyou. It turns out that I am using the same version of Ocaml.
However, looking at the build log, I think the fact that this is a 32bit
build of the binary might be the salient point. Let me see if I can
rebuild oxenstored as 32bit.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-31 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 4:29 [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm osstest service owner
2016-10-30 16:53 ` Andrew Cooper
2016-10-31 15:00 ` Wei Liu
2016-10-30 17:31 ` Andrew Cooper
2016-10-31 10:31 ` Ian Jackson
2016-10-31 10:37 ` Andrew Cooper [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 19:11 osstest service owner
2022-11-20 8:28 osstest service owner
2021-08-21 23:29 osstest service owner
2020-11-12 12:29 osstest service owner
2020-04-10 1:43 osstest service owner
2018-04-04 9:19 osstest service owner
2017-03-01 23:53 osstest service owner
2017-03-02 10:41 ` Daniel Kiper
2017-03-02 10:42 ` Andrew Cooper
2017-03-02 11:09 ` Daniel Kiper
2016-01-15 1:42 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=3eae69fe-f8ba-a159-8948-b0f75a942f45@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dave@recoil.org \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).