All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/6] iotests: throw away test timings if args change
Date: Tue, 20 Sep 2016 15:39:59 +0100	[thread overview]
Message-ID: <20160920143959.GR25490@redhat.com> (raw)
In-Reply-To: <d57a70f1-2acd-0494-cbbc-e7e8c93d76e2@redhat.com>

On Tue, Sep 20, 2016 at 09:38:33AM -0500, Eric Blake wrote:
> On 09/20/2016 09:15 AM, Daniel P. Berrange wrote:
> >>> I guess we could keep things simple by not inventing a new format,
> >>> but instead of using 'check.time', use 'check.time.$FORMAT-$PROTOCOL'
> >>> eg 'check.time.qcow2-file'
> >>
> >> Seems more palatable. Lots of files rather than lots of lines in a
> >> single file; searching is now fast (if you can come up with the right
> >> file name, the OS does the searching for you rather than us having to
> >> figure out which (if any) portion of a large file applies).  We may
> >> still want a command for easily cleaning everything, and if we do switch
> >> to new file names, we'll still want to clean up the old files.
> > 
> > Isn't that command called 'git clean -f'  - if we remove 'check.time'
> > from the gitignore file, it'll be deleted by a git clean, without
> > needing to ass the -i flag. I don't think we really need to reinvent
> > a special way to clean just these timing files, particularly since
> > they are not large.
> 
> I'd still rather have the gitignore file ignore anything that we don't
> want to check into the tree (I'm a big fan of 'git add -a .', and hate
> it when non-ignored generated files interfere with that; yes I know I
> can munge .git/info/exclude locally, but it feels cleaner when generated
> files are ignored at the project level).
> 
> But yes, relying on git to do the cleanup is fine from my point of view.

NB, I'd still suggest ignoring check.time-$FORMAT-BACKEND files since
those are current. I was just refering to removal of the legacy check.time
file so next git cleanup kills the obsolete file


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-09-20 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 17:35 [Qemu-devel] [PATCH 0/6] Improve I/O tests coverage of LUKS Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 1/6] iotests: throw away test timings if args change Daniel P. Berrange
2016-09-19 19:53   ` Eric Blake
2016-09-20  9:36     ` Daniel P. Berrange
2016-09-20 14:06       ` Eric Blake
2016-09-20 14:15         ` Daniel P. Berrange
2016-09-20 14:38           ` Eric Blake
2016-09-20 14:39             ` Daniel P. Berrange [this message]
2016-10-31 14:28               ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-10-31 14:34                 ` Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 2/6] iotests: fix remainining tests to work with LUKS Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 3/6] iotests: reduce PBKDF iterations when testing LUKS Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 4/6] iotests: add more LUKS hash combination tests Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 5/6] iotests: chown LUKS device before qemu-io launches Daniel P. Berrange
2016-09-19 17:35 ` [Qemu-devel] [PATCH 6/6] iotests: use _filter_qemu with test 140 Daniel P. Berrange

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=20160920143959.GR25490@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 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.