summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon McVittie <smcv@debian.org>2020-03-11 09:16:50 +0000
committerSimon McVittie <smcv@debian.org>2020-03-11 09:33:38 +0000
commit3058a0ed3aaf0a54058a96f884b0a73b0cc578a8 (patch)
tree75354d12425bbd8fbc2ce6e1229e24d8dd3fb97e
parent3857ea93dd3775d68010efed7ad3245714fee379 (diff)
downloadlibsoup-3058a0ed3aaf0a54058a96f884b0a73b0cc578a8.tar.gz
test-utils: Clarify meaning of an environment variable
SOUP_TESTS_IN_MAKE_CHECK used to be used for the Autotools build system. I mistakenly thought it was a way to skip the Apache-dependent tests during `make check`, but in fact the Autotools build system used to start a single instance of Apache, then run all the tests against that single instance, and finally shut it down. This mechanism is currently unused, but resurrecting it might be one way to avoid GNOME/libsoup#175.
-rw-r--r--tests/test-utils.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/tests/test-utils.c b/tests/test-utils.c
index bd1bab05..8b59a3dd 100644
--- a/tests/test-utils.c
+++ b/tests/test-utils.c
@@ -189,7 +189,9 @@ apache_cmd (const char *cmd)
void
apache_init (void)
{
- if (g_getenv ("SOUP_TESTS_IN_MAKE_CHECK"))
+ /* Set this environment variable if you are already running a
+ * suitably-configured Apache server */
+ if (g_getenv ("SOUP_TESTS_ALREADY_RUNNING_APACHE"))
return;
if (!apache_cmd ("start")) {