All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [ovmf test] 59044: trouble: blocked/broken/fail/pass
Date: Mon, 6 Jul 2015 11:35:46 +0100	[thread overview]
Message-ID: <1436178946.25646.30.camel@citrix.com> (raw)
In-Reply-To: <21914.22700.975480.13866@mariner.uk.xensource.com>

On Mon, 2015-07-06 at 11:30 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [ovmf test] 59044: trouble: blocked/broken/fail/pass"):
> > Seems to be Osstest/JobDB/Executive.pm line 137:
> >         die Dumper($ho)." ?" if $ho->{SharedOthers} && !
> >         $ho->{SharedReady};
> > So another sharing related glitch, like the linux-3.18 flight 59041 I
> > just pointedy ou at (which was on armhf though).
> > 
> > Any ideas?
> 
> This has the same root cause as the other mystery failure.
> 
> I hadn't appreciated that the checks in the host sharing machinery
> would mean that if a job allocates a share in a host, later steps in
> that job will fail if (in a subroutine of `selecthost') if they are
> run using a different version of osstest.  Having had the chance to
> think about it, I think this is probably for the best.

I agree.

> It does mean that in-place updates like I did will have a tendency to
> break ongoing builds.

They are a pretty rare event, and I suppose having realised this aspect
they might become rarer still..

Ian.

      reply	other threads:[~2015-07-06 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 22:40 [ovmf test] 59044: trouble: blocked/broken/fail/pass osstest service owner
2015-07-06  8:34 ` Ian Campbell
2015-07-06 10:30   ` Ian Jackson
2015-07-06 10:35     ` 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=1436178946.25646.30.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=osstest-admin@xenproject.org \
    --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.