From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: David Scott <dave@recoil.org>, Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
Date: Sun, 30 Oct 2016 17:31:46 +0000 [thread overview]
Message-ID: <df0b2fe4-66a4-be79-e85b-e05d3f786ecc@citrix.com> (raw)
In-Reply-To: <E1c0hkW-00006X-7O@osstest.test-lab.xenproject.org>
On 30/10/16 04:29, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
> testid debian-hvm-install
>
> Tree: linux git://xenbits.xen.org/linux-pvops.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: xen git://xenbits.xen.org/xen.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: xen git://xenbits.xen.org/xen.git
> Bug introduced: 0897514b4b376a167f968f79c6ea0dee1061458e
> Bug not present: 4000a7c7d7b0e01837abd3918e393f289c07d68c
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/101803/
>
>
> commit 0897514b4b376a167f968f79c6ea0dee1061458e
> Author: Andrew Cooper <andrew.cooper3@citrix.com>
> Date: Wed Oct 26 10:34:21 2016 +0100
>
> tools/oxenstored: Avoid allocating invalid transaction ids
Looking at xenstored-access.log before:
A8.1 write /vm/6fc3ae48-3d32-4710-aaac-55801d273773/uuid
6fc3ae48-3d32-4710-aaac-55801d273773
A8.1 write /vm/6fc3ae48-3d32-4710-aaac-55801d273773/name
debianhvm.guest.osstest
A8.1 write
/local/domain/1/control/platform-feature-multiprocessor-suspend 1
A8.1 write
/local/domain/1/control/platform-feature-xs_reset_watches 1
A8.1 commit
A8 write /libxl/1/dm-version qemu_xen_traditional
A8.2 write /local/domain/1/memory/static-max 5120000
A8.2 write /local/domain/1/memory/target 5115904
A8.2 write /local/domain/1/memory/videoram 4096
A8.2 write /local/domain/1/domid 1
And after:
A8.1 write /vm/0a3c1b35-33f8-432d-aab7-b98ea16d490f/uuid
0a3c1b35-33f8-432d-aab7-b98ea16d490f
A8.1 write /vm/0a3c1b35-33f8-432d-aab7-b98ea16d490f/name
debianhvm.guest.osstest
A8.1 write
/local/domain/1/control/platform-feature-multiprocessor-suspend 1
A8.1 write
/local/domain/1/control/platform-feature-xs_reset_watches 1
A8.1 commit
A8 write /libxl/1/dm-version qemu_xen_traditional
A8.1 write /local/domain/1/memory/static-max 5120000
A8.1 write /local/domain/1/memory/target 5115904
A8.1 write /local/domain/1/memory/videoram 4096
A8.1 write /local/domain/1/domid 1
the logging shows that almost all details are identical, other than the
transaction ids on successive transactions.
Compiling oxenstored locally on my dev box (and in the XenServer build
system) confirms that transaction ids behave as intended, i.e. ids are
allocated incrementally, even with the identified changeset in place.
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.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-30 17:31 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 [this message]
2016-10-31 10:31 ` Ian Jackson
2016-10-31 10:37 ` Andrew Cooper
-- 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=df0b2fe4-66a4-be79-e85b-e05d3f786ecc@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dave@recoil.org \
--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 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.