- 14 Jun, 2016 40 commits
-
-
Lasse Karstensen authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
a family of tickets related to it (#1933 #1920 #1898 (?) #1888 and #1865 (?))
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Lasse Karstensen authored
-
Dridi Boukelmoune authored
-
Nils Goroll authored
-
Nils Goroll authored
We may not have permission to unlink vp.dir $ /etc/init.d/varnish_master restart Stopping Varnish Cache: [FAILED] Starting Varnish Cache: Assert error in mgt_VccCompile(), mgt/mgt_vcc.c line 302: Condition((rmdir(vp.dir)) == 0) not true. errno = 13 (Permission denied)
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Lasse Karstensen authored
-
Poul-Henning Kamp authored
eat all CPU time.
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
I shouldn't rely on auto-complete too much, especially for only two characters...
-
Dridi Boukelmoune authored
Spotted by @fgsch
-
Dridi Boukelmoune authored
It also applies for the 4.1 and 4.0 series. Refs #1890
-
Dridi Boukelmoune authored
-
Federico G. Schwindt authored
Raise a ParseError exception if not. Fixes #1885.
-
Dridi Boukelmoune authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
When varnishtest creates a socket barrier, it will bind a socket and listen to incoming connections. Once the number of expected connections is open, connections are closed. Barrier users only need to connect to the socket, read "nothing" and block until the connection is closed. It allows virtually any process to sync with varnishtest. The barrier will provide macros with its socket information.
-
Dridi Boukelmoune authored
This is similar ASSERT_CLI, in order to make socket barriers creation thread-safe.
-
Dridi Boukelmoune authored
This is useful in HTTP loops where it's impossible to predict and use an array of barriers. All cycles expect the same number of waiters, unlike semaphores.
-
Dridi Boukelmoune authored
They work like semaphores, except that they need explicit initialization and can optionally be shared between processes. Conflicts: bin/varnishtest/tests/c00073.vtc
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
With this you can also filter based on logexpect's vsl arguments.
-
Lasse Karstensen authored
-
Poul-Henning Kamp authored
pattern in the body.
-
Lasse Karstensen authored
As suggested by Przemek Sobstel on github.
-
Guillaume Quintard authored
Spotted by: hermunn
-
Pål Hermunn Johansen authored
In most circumstances the counters vsm_overflow and vsm_overflowed should be zero. This patch tells the user what he should probably do when they are not.
-
Lasse Karstensen authored
(and test the commit email hook)
-