From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: John Hannfield <hal9020@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: 2.6.18 kernel status
Date: Tue, 06 Mar 2007 17:48:29 +0000 [thread overview]
Message-ID: <1173203309.4597.81.camel@localhost.localdomain> (raw)
In-Reply-To: <200703061744.19871.mark.williamson@cl.cam.ac.uk>
On Tue, 2007-03-06 at 17:44 +0000, Mark Williamson wrote:
> > > I think it's a case of "when the tests pass" rather than a regular push
> >
> > Oh ok. But from your experience when does this usually happen? Is it likely
> > to be a few days or weeks? I'm just trying to get a handle on when I should
> > re-try a hg pull to get this patch.
>
> I believe it can be a matter of hours if the tests pass first time. If one of
> the changesets in the staging tree causes the tests to fail then they'll all
> be stuck there until a fix is added and the tests finally pass - this can
> sometimes take a few days, I think, but shouldn't be the usual case.
There's a few gremlins in the testing infrastructure at the moment.
People are looking into it and it ought to pass soon ;-)
Ian.
next prev parent reply other threads:[~2007-03-06 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 23:53 2.6.18 kernel status John Hannfield
2007-03-06 10:28 ` Keir Fraser
2007-03-06 13:52 ` John Hannfield
2007-03-06 14:46 ` Mark Williamson
2007-03-06 17:13 ` John Hannfield
2007-03-06 17:44 ` Mark Williamson
2007-03-06 17:48 ` Ian Campbell [this message]
2007-03-06 17:19 ` Daniel P. Berrange
2007-03-06 17:29 ` Petersson, Mats
2007-03-06 17:37 ` Ian Pratt
2007-03-06 17:40 ` Daniel P. Berrange
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=1173203309.4597.81.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=hal9020@gmail.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.