xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hu <robert.hu@vmm.sh.intel.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Campbell <ian.campbell@citrix.com>,
	robert.hu@intel.com
Subject: Re: [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL
Date: Wed, 16 Dec 2015 09:39:07 +0800	[thread overview]
Message-ID: <1450229947.13553.2.camel@vmm.sh.intel.com> (raw)
In-Reply-To: <22128.19408.421764.423446@mariner.uk.xensource.com>

On Tue, 2015-12-15 at 17:20 +0000, Ian Jackson wrote:
> Ian Jackson writes ("Re: [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL"):
> > The Massachusetts instance is currently broken because the ownerdaemon
> > is broken.  So I am going to update the owner and queue daemons, and
> > restart everything, and then remove the Mass stop file.
> 
> The Mass owner daemon did not start because it runs on the DB VM which:
>   * Did not have /home/osstest/.xen-osstest/settings
>   * Did not have libhtml-parser-perl installed
> I have sorted this out.
> 
> > The Cambridge instance doesn't have the SQL locking changes yet, but
> > it would start testing the new osstest which might start to cause
> > trouble.  So I have dropped a stop file there now.  When Cambridge has
> > drained, probably tomorrow, I will update the daemons there (but not
> > push anything to the main in-use trees).
> > 
> > Any other instances (eg, Intel?) running in Executive mode need to get
> > the updates to the owner and queue daemons before starting to use the
> > new osstest.git for actual test flights.

Thanks for your care, Ian. My side instances only run in Standalone
mode.

> 
> Ian.

      reply	other threads:[~2015-12-16  1:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 16:26 [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL Ian Jackson
2015-12-15 16:26 ` [OSSTEST PATCH 2/4] Database locking: Perl: Increase retry count Ian Jackson
2015-12-15 16:33   ` Ian Campbell
2015-12-15 16:26 ` [OSSTEST PATCH 3/4] Database locking: Tcl: Cover LOCK TABLEs with catch Ian Jackson
2015-12-15 16:34   ` Ian Campbell
2015-12-15 16:26 ` [OSSTEST PATCH 4/4] Database locking: Tcl: Limit number of retries Ian Jackson
2015-12-15 16:35   ` Ian Campbell
2015-12-15 16:33 ` [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL Ian Campbell
2015-12-15 16:41   ` Ian Jackson
2015-12-15 16:47     ` Ian Campbell
2015-12-15 17:01     ` Ian Jackson
2015-12-15 17:20       ` Ian Jackson
2015-12-16  1:39         ` Robert Hu [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=1450229947.13553.2.camel@vmm.sh.intel.com \
    --to=robert.hu@vmm.sh.intel.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=robert.hu@intel.com \
    --cc=xen-devel@lists.xenproject.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).