From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, "xen.org" <ian.jackson@eu.citrix.com>
Subject: Re: [xen-unstable test] 22283: regressions - FAIL
Date: Thu, 5 Dec 2013 13:59:30 +0100 [thread overview]
Message-ID: <1386248370.5338.521.camel@Solace> (raw)
In-Reply-To: <1386246525.20047.48.camel@kazak.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2257 bytes --]
On gio, 2013-12-05 at 12:28 +0000, Ian Campbell wrote:
> On Thu, 2013-12-05 at 13:19 +0100, Dario Faggioli wrote:
> > On gio, 2013-12-05 at 09:31 +0000, Ian Campbell wrote:
> > > On Wed, 2013-12-04 at 19:13 +0000, xen.org wrote:
> >
> > > 2013-12-04 17:45:01 Z executing ssh ... osstest@10.80.246.74 rm -rf /local/scratch/osstest/osstest/build.22283.build-armhf && mkdir /local/scratch/osstest/osstest/build.22283.build-armhf
> > > Warning: Permanently added '10.80.246.74' (RSA) to the list of known hosts.
> > > mkdir: cannot create directory `/local/scratch/osstest/osstest/build.22283.build-armhf': No such file or directory
> > >
> > So, about these things... Why OSSTest does no create this (and other)
> > dirs himself if they're not present?
>
> In the general case, e.g. tmp and logs this is IMHO a bug (or several
> bugs) in osstest.
>
Ok.
> In this particular case /local/scratch/osstest is the osstest users
> $HOME and I think osstest should be entitled to assume that exists.
>
Right... I think I missed that part because I mostly look at test rather
than build failure reports.
> When we disabled builds on this machine I incorrectly removed this dir
> forgetting that it was $HOME and not just a scratch dir (which arises
> because osstest is a local user and not a not a global NIS user, and
> army uses NIS/autofs for /home)
>
Mmm... interesting. I tried to do something similar on another box, but
didn't manage to get to the end of it. I'll contact you either offline
or in a different thread about that. :-)
> > If that is the case then, given a bit of attention is necessary when
> > deploying it anyway, I don't think this buys us that much more "user
> > friendliness", while it certainly is something annoying. Personally, I
> > think it should just go ahead...
>
> Yes, for all cases apart from this one I think patches to add a suitable
> mkdir would be appreciated.
>
Sure, I'll look into this.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-05 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:13 [xen-unstable test] 22283: regressions - FAIL xen.org
2013-12-05 9:31 ` Ian Campbell
2013-12-05 12:19 ` Dario Faggioli
2013-12-05 12:28 ` Ian Campbell
2013-12-05 12:59 ` Dario Faggioli [this message]
2013-12-10 14:26 ` 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=1386248370.5338.521.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.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.