Re: [PATCH 0/6] modernize t1500

2 messages, 2 authors, 2016-06-16 · open the first message on its own page

Re: [PATCH 0/6] modernize t1500

From: Junio C Hamano <hidden>
Date: 2016-06-16 02:19:17

Junio C Hamano [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
quoted
Eric Sunshine [off-list ref] writes:
quoted
This series modernizes t1500; it takes an entirely different approach
than [1][2] and is intended to replace that series.
Turns out that it wasn't so painful after all.

The only small niggle I have is on 6/6; my preference would be,
because once we set up .git we do not add objects and refs to it, to
make a copy a lot earlier before the tests start.
-- >8 --
Subject: [PATCH 7/6] t1500: finish preparation upfront

The earlier tests do not attempt to modify the contents of .git (by
creating objects or refs, for example), which means that even if
some earlier tests before "cp -R" fail, the tests in repo.git will
run in an environment that we can expect them to succeed in.

Make it clear that tests in repo.git will be independent from the
results of earlier tests done in .git by moving its initialization
"cp -R .git repo.git" much higher in the test sequence.

Signed-off-by: Junio C Hamano <redacted>
---
I think the same logic applies to other preparatory things like
creation of sub/dir in the working tree etc.

Re: [PATCH 0/6] modernize t1500

From: Eric Sunshine <hidden>
Date: 2016-06-16 02:19:24

On Tue, May 10, 2016 at 2:26 PM, Junio C Hamano [off-list ref] wrote:
Junio C Hamano [off-list ref] writes:
quoted
Junio C Hamano [off-list ref] writes:
Subject: [PATCH 7/6] t1500: finish preparation upfront

The earlier tests do not attempt to modify the contents of .git (by
creating objects or refs, for example), which means that even if
some earlier tests before "cp -R" fail, the tests in repo.git will
run in an environment that we can expect them to succeed in.

Make it clear that tests in repo.git will be independent from the
results of earlier tests done in .git by moving its initialization
"cp -R .git repo.git" much higher in the test sequence.

Signed-off-by: Junio C Hamano <redacted>
---
I think the same logic applies to other preparatory things like
creation of sub/dir in the working tree etc.
Hmm, so are you suggesting a single 'setup' test at the start of
script which does the 'cp -R' and creates those other directories
needed by later tests?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help