All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 4607: regressions - FAIL
Date: Tue, 11 Jan 2011 12:30:53 +0000	[thread overview]
Message-ID: <C951FDFD.1178C%keir@xen.org> (raw)
In-Reply-To: <19756.19342.160120.151400@mariner.uk.xensource.com>

On 11/01/2011 12:22, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 4607: regressions -
> FAIL"):
>> hardens my suspicion that some of the tests (the leak-check/check
>> ones in particular based on past observation) fail and succeed
>> randomly. Shouldn't either tests that cause regular random false
>> negatives be removed from the set (or at least made non-blocking),
>> or regular random false positives imply that more than one run
>> must succeed before an automatic push?
> 
> You are indeed right.  And the more tests we add the smaller the
> bearable intermittent failure probability is.
> 
> I have changed the push gate logic so that it looks for tests of the
> same revision, in the way that you did by hand, and doesn't block the
> push if it finds that it passed in another run.
> 
> This ought to get us pushes more often.  It would still be nice to get
> rid of some of these race bugs :-).

Where are the races, do you think?

 -- Keir

> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-01-11 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  7:16 [xen-unstable test] 4607: regressions - FAIL xen.org
2011-01-07  9:08 ` Jan Beulich
2011-01-11 12:22   ` Ian Jackson
2011-01-11 12:30     ` Keir Fraser [this message]
2011-01-11 17:49       ` Ian Jackson

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=C951FDFD.1178C%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@novell.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 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.