Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
252ce718
Commit
252ce718
authored
Sep 25, 2018
by
Poul-Henning Kamp
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More 'vtest' vs. 'varnishtest' agnosticism.
parent
aba1633b
Changes
5
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
13 additions
and
11 deletions
+13
-11
huffman_gen.py
bin/varnishtest/huffman_gen.py
+1
-1
vtc_http.c
bin/varnishtest/vtc_http.c
+4
-4
vtc_main.c
bin/varnishtest/vtc_main.c
+3
-1
vtc_misc.c
bin/varnishtest/vtc_misc.c
+4
-4
vtc_process.c
bin/varnishtest/vtc_process.c
+1
-1
No files found.
bin/varnishtest/huffman_gen.py
View file @
252ce718
...
...
@@ -58,7 +58,7 @@ s = sym(63, 6, 0)
tbls
[
0xffffff
][
63
]
=
s
print
(
'''/* NB: This file is machine generated, DO NOT EDIT!
* edit
bin/varnishtest/huffman_input
instead
* edit
'huffman_input'
instead
*/
struct stbl;
...
...
bin/varnishtest/vtc_http.c
View file @
252ce718
...
...
@@ -76,9 +76,9 @@ extern const struct cmds http_cmds[];
*
* Be careful though, servers will by default listen to the 127.0.0.1 IP and
* will pick a random port, and publish 3 macros: sNAME_addr, sNAME_port and
* sNAME_sock, but only once they are started.
For varnishtest to
*
create the vcl with the correct values, the server must be started when you
*
use -vcl+backend
.
* sNAME_sock, but only once they are started.
*
For 'varnish -vcl+backend' to create the vcl with the correct values, the
*
server must be started first
.
*
* SECTION: client-server.args Arguments
*
...
...
@@ -1452,7 +1452,7 @@ cmd_http_chunked(CMD_ARGS)
/* SECTION: client-server.spec.chunkedlen
*
* chunkedlen NUMBER
* Do as ``chunked`` except that
varnishtest will generate the string
* Do as ``chunked`` except that
the string will be generated
* for you, with a length of NUMBER characters.
*/
...
...
bin/varnishtest/vtc_main.c
View file @
252ce718
...
...
@@ -597,7 +597,9 @@ main(int argc, char * const *argv)
params_vsb
=
VSB_new_auto
();
AN
(
params_vsb
);
p
=
getenv
(
"VARNISHTEST_DURATION"
);
p
=
getenv
(
"VTEST_DURATION"
);
if
(
p
==
NULL
)
p
=
getenv
(
"VARNISHTEST_DURATION"
);
if
(
p
!=
NULL
)
vtc_maxdur
=
atoi
(
p
);
...
...
bin/varnishtest/vtc_misc.c
View file @
252ce718
...
...
@@ -112,8 +112,8 @@ cmd_varnishtest(CMD_ARGS)
*
* By default a zero exit code is expected, otherwise the vtc will fail.
*
* Notice that the commandstring is prefixed with "exec 2>&1;" to
join
* stderr and stdout back to the
varnish
test process.
* Notice that the commandstring is prefixed with "exec 2>&1;" to
combine
* stderr and stdout back to the test process.
*
* Optional arguments:
*
...
...
@@ -352,9 +352,9 @@ cmd_delay(CMD_ARGS)
* dns
* DNS lookups are working
* topbuild
*
varnish
test has been started with '-i'
*
The
test has been started with '-i'
* root
*
varnish
test has been invoked by the root user
*
The
test has been invoked by the root user
* user_varnish
* The varnish user is present
* user_vcache
...
...
bin/varnishtest/vtc_process.c
View file @
252ce718
...
...
@@ -856,7 +856,7 @@ process_close(struct process *p)
* Shorthand for -start -wait.
*
* In most cases, if you just want to start a process and wait for it
* to finish, you can use the
varnishtest
``shell`` command instead.
* to finish, you can use the ``shell`` command instead.
* The following commands are equivalent::
*
* shell "do --something"
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment