[PATCH 0 of 4] Begin adding tests and small fixes for Largefiles Extension
Matt Mackall
mpm at selenic.com
Thu Oct 6 16:18:45 CDT 2011
On Thu, 2011-10-06 at 21:21 +0200, Na'Tosha Bard wrote:
> 2011/10/6 Matt Mackall <mpm at selenic.com>
>
> > On Thu, 2011-10-06 at 11:22 +0200, Na'Tosha Bard wrote:
> > > NOTE: This replaces the previous patchbomb.
> > >
> > > This patchbomb starts the process of adding tests (and fixes for
> > > things I find as I write the tests) for the largefiles extension.
> > > These tests cover basic functionality of mercurial operations on
> > > largefiles, as well as some more obscure functionality that I know to
> > > have been very problematic (hard to fix and easy to break) for
> > > largefiles in the past.
> >
> > We need to merge these tests together. They're hugely redundant, and
> > thus slow:
> >
> > Test 1:
> > - enable largefiles
> > - create a repo
> > - create some files
> > - add some files
> > - call status
> >
> > Test 2:
> > - enable largefiles
> > - create a repo
> > - create some files
> > - add some files
> > - call status
> > - commit
> >
> > Test 3:
> > - enable largefiles
> > - create a repo
> > - create some files
> > - add some files
> > - call status
> > - commit
> > - remove some files
> >
> > Let's try to put everything into a single test-largefiles.t until we
> > find a reason to split things up.
>
>
> OK, I'll start again tomorrow and send a new patch. The bugfix for the
> os.link function should still go in, I think. I don't see a reason to send
> a new patch for that.
Sure, it's sitting in my inbox until I get enough work-in-progress
cleared away to queue it.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list