Re: [PATCH 1/4] t5510: start tracking-ref tests from a known state
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- May 14, 2013, 22:18 UTC
- Message-ID
- <CAPig+cQk2GCL4z=xo1m86uvKzE2QrP_1ajzkJvDTadxV_dkDuw@mail.gmail.com>
- In-Reply-To
- <20130511161400.GA3270@sigill.intra.peff.net>
On Sat, May 11, 2013 at 12:14 PM, Jeff King <peff@peff.net> wrote:
> We have three sequential tests for for whether tracking refs
s/for for/for/ [or] s/for for/for checking/
Show 12 quoted lines
> are updated by various fetches and pulls; the first two > should not update the ref, and the third should. Each test > depends on the state left by the test before. > > This is fragile (a failing early test will confuse later > tests), and means we cannot add more "should update" tests > after the third one. > > Let's instead save the initial state before these tests, and > then reset to a known state before running each test. > > Signed-off-by: Jeff King <peff@peff.net>