All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-4.9-testing test] 133881: regressions - FAIL
Date: Tue, 19 Mar 2019 02:50:52 -0600	[thread overview]
Message-ID: <5C90AD6C020000780022029A@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <osstest-133881-mainreport@xen.org>

>>> On 19.03.19 at 01:39, <osstest-admin@xenproject.org> wrote:
> flight 133881 xen-4.9-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/133881/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 132889
>  test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 132889

I've looked into these (and also the corresponding 4.8 one) before,
without being able to spot anything that would provide some sort of
hint to me as to what's actually going wrong. All I notice is

error: Timed out during operation: cannot acquire state change lock

But I have a hard time seeing how this can be a result of the
changes under test (I assume the state change lock is a tools thing,
and there are no pending tools changes). Yet judging from ...

> Last test of basis   132889  2019-02-04 22:04:09 Z   42 days
> Failing since        133147  2019-02-11 13:41:50 Z   35 days   24 attempts
> Testing same since   133603  2019-03-05 18:49:35 Z   13 days    9 attempts

... this there's probably no hope anymore for this to go away all
by itself. Could someone else please also look into these? I
wonder if the failures are connected to the tests now running
(stickily) on the merlots.

The above time line also suggests that the problem started to
appear with the version update, which can't possibly have
caused a regression on its own.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2019-03-19  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  0:39 [xen-4.9-testing test] 133881: regressions - FAIL osstest service owner
2019-03-19  8:50 ` Jan Beulich [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=5C90AD6C020000780022029A@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=osstest-admin@xenproject.org \
    --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 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.