From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, ian.jackson@eu.citrix.com
Subject: Re: [xen-unstable baseline test] 30923: tolerable FAIL
Date: Mon, 27 Oct 2014 14:11:25 +0000 [thread overview]
Message-ID: <1414419085.23883.19.camel@citrix.com> (raw)
In-Reply-To: <544E558E020000780004272E@mail.emea.novell.com>
On Mon, 2014-10-27 at 13:24 +0000, Jan Beulich wrote:
> Considering that this is a baseline test, won't this result in pushes
> as soon as no less than the set of failures occurs in a future run
> (like would almost have been the case with flight 30959)?
I'm not sure. Ian is back tomorrow.
> Independent of that - having looked at a couple of failures, I
> didn't really manage to spot what is going wrong here in such a
> massive way. Was there an infrastructure issue over the
> weekend?
I see a lot of:
2014-10-25 13:07:34 Z FAILURE: guest debian.guest.osstest 5a:36:0e:cb:00:06 22 link/ip/tcp: wait timed out: woking.cam.xci-test.com:5556:1: unknown syntax.
this is trying to read/parse the leases file.
Looking at the stashed leases file I see
http://www.chiark.greenend.org.uk/~xensrcts/logs/30923/test-amd64-amd64-xl/dhcpleases-debian.bad
mkdir: cannot create directory `trace.1414242454.32588': Too many links
I suppose this is something to do with the hacks Ian has been doing to
try and track down the issue with the leases file sometimes not
existing. I'm going to go have a poke around now and see if I can work
out what is going on...
Ian.
next prev parent reply other threads:[~2014-10-27 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 9:36 [xen-unstable baseline test] 30923: tolerable FAIL xen.org
2014-10-27 13:24 ` Jan Beulich
2014-10-27 14:11 ` Ian Campbell [this message]
2014-10-27 14:16 ` Ian Campbell
2014-10-28 10:51 ` 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=1414419085.23883.19.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.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).