All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [Qemu-devel] [kvm-unit-tests PATCH v6 2/3] run_tests: put logs into per-test file
Date: Thu, 12 Jan 2017 18:35:57 +0800	[thread overview]
Message-ID: <20170112103557.GP4450@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170112100405.tyroqjvxpxdxocuc@hawk.localdomain>

On Thu, Jan 12, 2017 at 11:04:05AM +0100, Andrew Jones wrote:

[...]

> >  config=$TEST_DIR/unittests.cfg
> > -rm -f test.log
> > -printf "BUILD_HEAD=$(cat build-head)\n\n" > test.log
> > +
> > +rm -rf $unittest_log_dir.old
> > +[ -d $unittest_log_dir ] && mv $unittest_log_dir $unittest_log_dir.old
> > +mkdir $unittest_log_dir || exit 2
> > +
> > +echo "BUILD_HEAD=$(cat build-head)" > $unittest_log_dir/SUMMARY
> > +
> 
> nit: to be 100% correct all the references to the log dir should have
> "'s around them in order to handle spaces, or other shell ambiguous
> characters, in the name. For example, mkdir $log_dir, where $log_dir
> is "my tests" would create two directories, "my" and "tests" without
> the quotes. Anyway, I'm not too worried about someone choosing a
> weird log dir name, nor even changing it from the default.
> 
> Isn't bash fun :-)

It is, as long as it won't break my system... (Once I accidentally did
a "rm -rf /lib" in Bash when I was still using FreeBSD... Bash became
less funny since then ;-).

I'll add them if I'm going to have another spin.

[...]

> Reviewed-by: Andrew Jones <drjones@redhat.com>

Thanks for reviewing!

-- peterx

  reply	other threads:[~2017-01-12 10:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  3:36 [kvm-unit-tests PATCH v6 0/3] run_tests: support concurrent test execution Peter Xu
2017-01-12  3:36 ` [Qemu-devel] " Peter Xu
2017-01-12  3:36 ` [kvm-unit-tests PATCH v6 1/3] run_tests: fix errno for param parsing Peter Xu
2017-01-12  3:36   ` [Qemu-devel] " Peter Xu
2017-01-12 11:42   ` Andrew Jones
2017-01-12  3:36 ` [kvm-unit-tests PATCH v6 2/3] run_tests: put logs into per-test file Peter Xu
2017-01-12  3:36   ` [Qemu-devel] " Peter Xu
2017-01-12 10:04   ` Andrew Jones
2017-01-12 10:35     ` Peter Xu [this message]
2017-01-12 12:55   ` Paolo Bonzini
2017-01-12 12:55     ` [Qemu-devel] " Paolo Bonzini
2017-01-12 14:14     ` Peter Xu
2017-01-12 14:14       ` [Qemu-devel] " Peter Xu
2017-01-12  3:36 ` [kvm-unit-tests PATCH v6 3/3] run_tests: allow run tests in parallel Peter Xu
2017-01-12  3:36   ` [Qemu-devel] " Peter Xu
2017-01-12 11:42   ` Andrew Jones
2017-01-12 13:31     ` Paolo Bonzini

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=20170112103557.GP4450@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.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.