Ilya Bobyr ilya.bo...@gmail.com writes:
While it could be done, it looks less obvious than this:
GIT_TEST_ONLY='1 4' ./t0001-init.sh
If you are thinking about affecting only one test, then you
shouldn't be mucking with environment variables in the first place,
primarily because running:
On 3/4/2014 12:29 AM, Junio C Hamano wrote:
Ilya Bobyr ilya.bo...@gmail.com writes:
While it could be done, it looks less obvious than this:
GIT_TEST_ONLY='1 4' ./t0001-init.sh
If you are thinking about affecting only one test,
Yes, that is the use case: when I am developing a
Ilya Bobyr ilya.bo...@gmail.com writes:
On 3/4/2014 12:29 AM, Junio C Hamano wrote:
...
then you
shouldn't be mucking with environment variables in the first place,
primarily because running:
$ GIT_TEST_ONLY='1 4' make test
to run test .1 and .4 of all the test scripts would not
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging.
---
t/README | 15 +++
t/test-lib.sh |8
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/t/README b/t/README
index caeeb9d..f939987 100644
--- a/t/README
+++ b/t/README
@@
Minor nits.
From: Ilya Bobyr ilya.bo...@gmail.com
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when
debugging.
---
t/README | 15 +++
t/test-lib.sh |8
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/t/README b/t/README
index
On Mon, Mar 3, 2014 at 5:24 AM, Ilya Bobyr ilya.bo...@gmail.com wrote:
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging.
To be grammatically similar to GIT_SKIP_TESTS, perhaps name it GIT_RUN_TESTS?
---
t/README | 15 +++
t/test-lib.sh |8
On 3/3/2014 3:03 PM, Eric Sunshine wrote:
On Mon, Mar 3, 2014 at 5:24 AM, Ilya Bobyr ilya.bo...@gmail.com wrote:
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging.
To be grammatically similar to GIT_SKIP_TESTS, perhaps name it GIT_RUN_TESTS?
There is actually an upside
Eric Sunshine sunsh...@sunshineco.com writes:
On Mon, Mar 3, 2014 at 5:24 AM, Ilya Bobyr ilya.bo...@gmail.com wrote:
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging.
To be grammatically similar to GIT_SKIP_TESTS, perhaps name it GIT_RUN_TESTS?
I actually do not like
On 3/3/2014 3:26 PM, Junio C Hamano wrote:
Eric Sunshine sunsh...@sunshineco.com writes:
On Mon, Mar 3, 2014 at 5:24 AM, Ilya Bobyr ilya.bo...@gmail.com wrote:
This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging.
To be grammatically similar to GIT_SKIP_TESTS, perhaps name
Ilya Bobyr ilya.bo...@gmail.com writes:
It might be that we are looking at different use cases, as you are
talking about whole test suits.
I do not think so.
I do not see anything prevents you from saying
GIT_SKIP_TESTS='t !t.1 !t.4'
to specify test-pieces in individual
On 3/3/2014 4:08 PM, Junio C Hamano wrote:
Ilya Bobyr ilya.bo...@gmail.com writes:
It might be that we are looking at different use cases, as you are
talking about whole test suits.
I do not think so.
Good :)
I am trying to understand the use cases. And make sure we are talking
about the
11 matches
Mail list logo
