All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/5] Enhance fs tests
Date: Wed, 14 Sep 2016 09:38:55 -0400	[thread overview]
Message-ID: <20160914133855.GD8156@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ1Rz7knPxd2guDnLobOkwzPRJ7EjVgUBHQLx=vwrmq1hw@mail.gmail.com>

On Wed, Sep 14, 2016 at 07:32:47AM -0600, Simon Glass wrote:
> Hi Stefan,
> 
> On 13 September 2016 at 17:01, Stefan Br?ns
> <stefan.bruens@rwth-aachen.de> wrote:
> > The first 3 patches do some cleanups for the current test, especially TC11
> > had some issues (strange match for expected output, use of unitialized
> > variable).
> >
> > The last two patches add test cases for handling ".". Ext4 used to crash,
> > as a match on the first entry of a directory block was not handled
> > correctly.
> 
> I think we should move these to pytest before enhancing them.

For the moment, I disagree.  We have fs issues, and we're fixing fs
issues and getting tests while we're doing that is important.  It would
be good, and would make my (and everyone else that has one too) setup
easier if these were migrated but I don't want to blocks more tests on
having them be made into different but equivalent tests first.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160914/daf4532c/attachment.sig>

  reply	other threads:[~2016-09-14 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 23:01 [U-Boot] [PATCH v2 0/5] Enhance fs tests Stefan Brüns
2016-09-14 13:32 ` Simon Glass
2016-09-14 13:38   ` Tom Rini [this message]
2016-09-14 14:22     ` Simon Glass

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=20160914133855.GD8156@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.