git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/2] add missing LIBCURL prereq to a few tests
@ 2024-09-11 10:30 Martin Ågren
  2024-09-11 10:30 ` [PATCH 1/2] t1517: add missing LIBCURL prereq Martin Ågren
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Martin Ågren @ 2024-09-11 10:30 UTC (permalink / raw)
  To: git; +Cc: Junio C Hamano, Jeff Hostetler

Hi,

I recently had reason to build Git without libcurl. That surfaced two
test scripts that use `git http-fetch` or similar without giving the
LIBCURL prerequisite.

Martin

Martin Ågren (2):
  t1517: add missing LIBCURL prereq
  t0211: add missing LIBCURL prereq

 t/t0211-trace2-perf.sh  | 6 ++++--
 t/t1517-outside-repo.sh | 2 +-
 2 files changed, 5 insertions(+), 3 deletions(-)

-- 
2.46.0.733.g1eb83ef1a1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH 1/2] t1517: add missing LIBCURL prereq
  2024-09-11 10:30 [PATCH 0/2] add missing LIBCURL prereq to a few tests Martin Ågren
@ 2024-09-11 10:30 ` Martin Ågren
  2024-09-11 10:31 ` [PATCH 2/2] t0211: " Martin Ågren
  2024-09-11 15:53 ` [PATCH 0/2] add missing LIBCURL prereq to a few tests Junio C Hamano
  2 siblings, 0 replies; 4+ messages in thread
From: Martin Ågren @ 2024-09-11 10:30 UTC (permalink / raw)
  To: git; +Cc: Junio C Hamano

After building Git with NO_LIBCURL, there is no `git remote-http`, so
it's not meaningful to test that it can run outside of a repository.
Indeed, that test will fail. Add the LIBCURL prereq to it.

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
 This is from b25ec8b8d5 (t1517: more coverage for commands that work
 without repository, 2024-05-31), which first appeared in 2.46.0.

 t/t1517-outside-repo.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/t1517-outside-repo.sh b/t/t1517-outside-repo.sh
index 990a036582..342defbb61 100755
--- a/t/t1517-outside-repo.sh
+++ b/t/t1517-outside-repo.sh
@@ -98,7 +98,7 @@ test_expect_success 'stripspace outside repository' '
 	nongit git stripspace -s </dev/null
 '
 
-test_expect_success 'remote-http outside repository' '
+test_expect_success LIBCURL 'remote-http outside repository' '
 	test_must_fail git remote-http 2>actual &&
 	test_grep "^error: remote-curl" actual &&
 	(
-- 
2.46.0.733.g1eb83ef1a1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* [PATCH 2/2] t0211: add missing LIBCURL prereq
  2024-09-11 10:30 [PATCH 0/2] add missing LIBCURL prereq to a few tests Martin Ågren
  2024-09-11 10:30 ` [PATCH 1/2] t1517: add missing LIBCURL prereq Martin Ågren
@ 2024-09-11 10:31 ` Martin Ågren
  2024-09-11 15:53 ` [PATCH 0/2] add missing LIBCURL prereq to a few tests Junio C Hamano
  2 siblings, 0 replies; 4+ messages in thread
From: Martin Ågren @ 2024-09-11 10:31 UTC (permalink / raw)
  To: git; +Cc: Jeff Hostetler

After building Git with NO_LIBCURL, we're lacking `git remote-http` and
`git http-fetch`, so when we test that they trace as they should, we're
bound to fail. Add the LIBCURL prereq to those tests.

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
 This is from around 6111252cbf (trace2: emit 'def_param' set with
 'cmd_name' event, 2024-03-07), which first appeared in 2.45.0.

 t/t0211-trace2-perf.sh | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/t/t0211-trace2-perf.sh b/t/t0211-trace2-perf.sh
index 070fe7a5da..dddc130560 100755
--- a/t/t0211-trace2-perf.sh
+++ b/t/t0211-trace2-perf.sh
@@ -337,7 +337,8 @@ test_expect_success 'expect def_params for query command' '
 # remote-curl.c rather than git.c.  Confirm that we get def_param
 # events from both layers.
 #
-test_expect_success 'expect def_params for remote-curl and _run_dashed_' '
+test_expect_success LIBCURL \
+		'expect def_params for remote-curl and _run_dashed_' '
 	test_when_finished "rm prop.perf actual" &&
 
 	test_config_global "trace2.configParams" "cfg.prop.*" &&
@@ -366,7 +367,8 @@ test_expect_success 'expect def_params for remote-curl and _run_dashed_' '
 # an executable built from http-fetch.c.  Confirm that we get
 # def_param events from both layers.
 #
-test_expect_success 'expect def_params for http-fetch and _run_dashed_' '
+test_expect_success LIBCURL \
+		'expect def_params for http-fetch and _run_dashed_' '
 	test_when_finished "rm prop.perf actual" &&
 
 	test_config_global "trace2.configParams" "cfg.prop.*" &&
-- 
2.46.0.733.g1eb83ef1a1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH 0/2] add missing LIBCURL prereq to a few tests
  2024-09-11 10:30 [PATCH 0/2] add missing LIBCURL prereq to a few tests Martin Ågren
  2024-09-11 10:30 ` [PATCH 1/2] t1517: add missing LIBCURL prereq Martin Ågren
  2024-09-11 10:31 ` [PATCH 2/2] t0211: " Martin Ågren
@ 2024-09-11 15:53 ` Junio C Hamano
  2 siblings, 0 replies; 4+ messages in thread
From: Junio C Hamano @ 2024-09-11 15:53 UTC (permalink / raw)
  To: Martin Ågren; +Cc: git, Jeff Hostetler

Martin Ågren <martin.agren@gmail.com> writes:

> Hi,
>
> I recently had reason to build Git without libcurl. That surfaced two
> test scripts that use `git http-fetch` or similar without giving the
> LIBCURL prerequisite.
>
> Martin
>
> Martin Ågren (2):
>   t1517: add missing LIBCURL prereq
>   t0211: add missing LIBCURL prereq
>
>  t/t0211-trace2-perf.sh  | 6 ++++--
>  t/t1517-outside-repo.sh | 2 +-
>  2 files changed, 5 insertions(+), 3 deletions(-)

Thanks.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-09-11 15:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-09-11 10:30 [PATCH 0/2] add missing LIBCURL prereq to a few tests Martin Ågren
2024-09-11 10:30 ` [PATCH 1/2] t1517: add missing LIBCURL prereq Martin Ågren
2024-09-11 10:31 ` [PATCH 2/2] t0211: " Martin Ågren
2024-09-11 15:53 ` [PATCH 0/2] add missing LIBCURL prereq to a few tests Junio C Hamano

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).