All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 118441: regressions - trouble: blocked/broken/fail/pass
Date: Tue, 30 Jan 2018 16:02:20 +0000	[thread overview]
Message-ID: <23152.38668.802028.222240@mariner.uk.xensource.com> (raw)
In-Reply-To: <c1236676-e73b-5b85-379d-71d2cd64e5f1@arm.com>

Julien Grall writes ("Re: [Xen-devel] [xen-unstable test] 118441: regressions - trouble: blocked/broken/fail/pass"):
..
> failure (trapped): status 65280 at Osstest/TestSupport.pm line 486.

The real error is this:

  Connection closed by 172.16.144.44 port 22

At 2018-01-29 19:15:29 Z.  This is mysterious to me.  I think that
message means that the osstest controller's ssh client got a TCP
connection close.  It was running an innocuous and short-running
information gathering command.

I looked in all of the logs from /var/log (apart from the ones from
the installer) and none of them show anything at this time.  The next
test step was able to ssh to the box just fine.

It seems that the sshd servicing this particular request just exited
and there is no explanation.

The DHCP leases seem to be being renewed very frequently (every 4 mins
AFAICT, although the server default lease time is 10 mins) but this
should not cause lossage.  In any case the previous renewal was
19:13:40 so the next one wouldn't be until 19:17, ie after the
failure.

Ian.

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

      reply	other threads:[~2018-01-30 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 15:44 [xen-unstable test] 118441: regressions - trouble: blocked/broken/fail/pass osstest service owner
2018-01-30 15:49 ` Julien Grall
2018-01-30 16:02   ` Ian Jackson [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=23152.38668.802028.222240@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.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.