From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Paul Durrant <xadimgnik@gmail.com>
Subject: [OSSTEST PATCH 2/4] standalone-generate-dump-flight-runvars: mkdir -p logs
Date: Tue, 16 Jun 2020 17:58:10 +0100 [thread overview]
Message-ID: <20200616165812.25380-2-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20200616165812.25380-1-ian.jackson@eu.citrix.com>
Otherwise if logs doesn't exist, the code in `standalone' which is
eventually called to build each flight will try to do it - but that
code is not idempotent in the presence of other racing copies of
itself.
Rather than trusting mkdir -p there, do it here.
No change other than to this dev-debugging script.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
standalone-generate-dump-flight-runvars | 1 +
1 file changed, 1 insertion(+)
diff --git a/standalone-generate-dump-flight-runvars b/standalone-generate-dump-flight-runvars
index 3b893623..5c93b0af 100755
--- a/standalone-generate-dump-flight-runvars
+++ b/standalone-generate-dump-flight-runvars
@@ -53,6 +53,7 @@ if [ "x$AP_FETCH_PLACEHOLDERS" != xy ]; then
mkdir tmp/apmemo
fi
export AP_FETCH_PFX='./memoise tmp/apmemo'
+ mkdir -p logs
fi
# In the future it might be nice for this script to arrange to use a
--
2.20.1
next prev parent reply other threads:[~2020-06-16 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 16:58 [OSSTEST PATCH 1/4] standalone: Fix spurious ] Ian Jackson
2020-06-16 16:58 ` Ian Jackson [this message]
2020-06-16 16:58 ` [OSSTEST PATCH 3/4] standalone: Do not complain about ssh if AP_FETCH_PLACEHOLDERS=y Ian Jackson
2020-06-16 16:58 ` [OSSTEST PATCH 4/4] make-flight: Test Xen 4.9 and Xen 4.10 on stretch 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=20200616165812.25380-2-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xadimgnik@gmail.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).