From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: Proposed force push of staging to master
Date: Mon, 17 Feb 2014 14:00:43 +0000 [thread overview]
Message-ID: <5302160B.70601@eu.citrix.com> (raw)
In-Reply-To: <21249.64449.582039.323772@mariner.uk.xensource.com>
On 02/17/2014 12:08 PM, Ian Jackson wrote:
> xen.org writes ("[xen-unstable test] 24870: regressions - trouble: broken/fail/pass"):
>> flight 24870 xen-unstable real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/24870/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> build-i386-oldkern 3 host-build-prep fail REGR. vs. 24862
> This was the "usual" failure: Citrix's intercepting web proxy causes
> some hg clones of linux-2.6.18.hg from xenbits to fail. The rest of
> the flight was successful.
>
> The rest of the weekend's tests were badly affected by a disk failure
> on earwig. So as a result we didn't get a push.
>
> I cleared out a bunch of other stuff running in the test system in an
> effort to get a pass sooner, but peeking at the results the same job
> has failed the same way in the currently-running flight. So we won't
> get a push in that iteration either.
>
> We should consider doing a force push for RC4. The risks are:
> * There is something actually wrong with xen.git which causes the
> 32-bit 2.6.18 build to fail;
> * Less resistance in the future to 2.6.18 build failures.
> I'll discuss these in turn.
>
> The build-*-oldkern tests involve using the kernel-building machinery
> in xen.git to clone 2.6.18 from xenbits and build it. Firstly, I think
> it's unlikely that anything in xen.git#d883c179..4e8d89bc would affect
> that. Secondly, the build-amd64-oldkern builds have passed. So I
> think we can almost entirely discount the first risk.
>
> I think the second risk is tolerable. We should keep an eye on it for
> a bit and if it turns out that the oldkern build really does become
> broken later and as a result keeps failing indefinitely, we will be
> able to spot that.
>
> So, we propose to push 4e8d89bc1445f91c4c6c7bf0ad8d51b0c809841e to
> xen.git#master and call it RC4. Comments welcome.
Thanks for the analysis. This seems like a good plan.
-George
next prev parent reply other threads:[~2014-02-17 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 9:35 [xen-unstable test] 24870: regressions - trouble: broken/fail/pass xen.org
2014-02-17 12:08 ` Proposed force push of staging to master Ian Jackson
2014-02-17 12:42 ` Jan Beulich
2014-02-17 14:00 ` George Dunlap [this message]
2014-02-17 16:49 ` Ian Jackson
2014-02-18 10:11 ` Jan Beulich
2014-02-18 11:30 ` Proposed force push of staging to master [and 1 more messages] Ian Jackson
2014-02-18 10:57 ` Proposed force push of staging to master Stefano Stabellini
2014-02-18 11:58 ` Ian Campbell
2014-02-18 11:59 ` Ian Campbell
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=5302160B.70601@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--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 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).