From: Ian Campbell <ian.campbell@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <JBeulich@suse.com>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH V3] libxl: Increase device model startup timeout to 1min.
Date: Tue, 14 Jul 2015 15:48:05 +0100 [thread overview]
Message-ID: <1436885285.25044.91.camel@citrix.com> (raw)
In-Reply-To: <1436883827.13522.149.camel@citrix.com>
On Tue, 2015-07-14 at 16:23 +0200, Dario Faggioli wrote:
> BTW, Ian, perhaps it's not that urgent, but how cumbersome would it be
> to setup a few ad-hoc flights, like you did here:
>
> http://logs.test-lab.xenproject.org/osstest/logs/58853/
>
> when also doing what Anthony was doing for stracing QEMU,
"Fairly cumbersome", someone would have to develop and test some code in
osstest to allow the switching in of a device model wrapper and for
collecting the results afterwards.
Those previous adhoc flights were simple because they just involved
rerunning existing jobs in the same configuration and with the same
harness code.
I'm afraid that for a "to see what we see" experiment the effort I have
outweighs the predicted information gain for this.
If someone were to provide a tested and working osstest patch I could
probably throw it through a few runs with minimal effort though.
> as he
> described in here:
>
> http://bugs.xenproject.org/xen/mid/%3C20150624133948.GJ3393@perard.uk.xensource.com%3E
>
> I'm not sure what we could find, nor whether we should expect the strace
> to be similar to Anthony's. Perhaps not, as the system here is idle, and
> perhaps something would highlight or hint at where to look in this
> specific case... Or maybe none of the above, but it may be worth a try.
>
> If there is anything I can do for helping setting this up, just let me
> know (here or on IRC).
>
> Regards,
> Dario
prev parent reply other threads:[~2015-07-14 14:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:57 [PATCH] libxl: Increase device model startup timeout to 1min Anthony PERARD
2015-06-26 16:41 ` Ian Campbell
2015-06-29 14:23 ` Anthony PERARD
2015-06-29 14:51 ` Ian Campbell
2015-06-29 16:09 ` Anthony PERARD
2015-06-30 3:08 ` Dario Faggioli
2015-06-30 14:04 ` Ian Jackson
2015-06-30 15:58 ` Stefano Stabellini
2015-06-30 16:40 ` Ian Jackson
2015-07-01 15:03 ` Stefano Stabellini
2015-07-02 11:11 ` Anthony PERARD
2015-07-02 12:38 ` Ian Jackson
2015-07-03 11:21 ` Anthony PERARD
2015-07-03 11:30 ` Ian Jackson
2015-07-07 13:44 ` Ian Campbell
2015-07-07 13:47 ` Ian Jackson
2015-07-07 14:37 ` [PATCH V2] " Anthony PERARD
2015-07-07 14:41 ` Ian Jackson
2015-07-07 15:09 ` [PATCH V3] " Anthony PERARD
2015-07-07 15:14 ` Ian Jackson
2015-07-07 15:41 ` Ian Campbell
2015-07-14 6:17 ` Jan Beulich
2015-07-14 7:55 ` Ian Campbell
2015-07-14 9:25 ` Dario Faggioli
2015-07-14 9:37 ` Ian Campbell
2015-07-14 10:52 ` Dario Faggioli
2015-07-14 14:23 ` Dario Faggioli
2015-07-14 14:48 ` Ian Campbell [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=1436885285.25044.91.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=stefano.stabellini@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).