- 18 Nov, 2019 8 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
we are going to need to check a temperature on its own
-
Nils Goroll authored
Ref #3094
-
Nils Goroll authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Martin Blix Grydeland authored
Fix a small memory leak when failing to spawn a new thread.
-
Martin Blix Grydeland authored
When getidleworker signals the pool herder to spawn a thread, it increases the dry counter, and the herder resets dry again when spawning a single thread. This will in many cases only create a single thread even though the herder was signaled dry multiple times, and may cause a situation where the cache acceptor is queued and no new thread is created. Together with long lasting tasks (ie endless pipelines), and all other tasks having higher priority, this will prevent the cache acceptor from being rescheduled. c00096.vtc demonstrates how this can lock up. To fix this, spawn threads if we have queued tasks and we are below the thread maximum level.
-
- 17 Nov, 2019 1 commit
-
-
Deepjyoti Mondal authored
Fixed the typos in the files mentioned in the corresponding issue.
-
- 16 Nov, 2019 3 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
Fixes #3135
-
Emmanuel Hocdet authored
-
- 15 Nov, 2019 2 commits
-
-
Dridi Boukelmoune authored
Otherwise you might run into this: Message from VCC-compiler: Unused backend nil, defined: ('<vcl.inline>' Line 4 Pos 17) backend nil none; ----------------###------ (That was just a warning) Message from C-compiler: vgc.c:1476:20: error: unused variable 'vgc_backend_nil' [-Werror,-Wunused-variable] static VCL_BACKEND vgc_backend_nil; ^ 1 error generated. Running C-compiler failed, exited with 1 VCL compilation failed This is done in both init and discard code to maintain the balance.
-
Dridi Boukelmoune authored
This reverts commit 1d23a733.
-
- 14 Nov, 2019 4 commits
-
-
Emmanuel Hocdet authored
Fixes #3131
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
Because someone brought a suncc to a vtest party.
-
Dridi Boukelmoune authored
Now that vtc.typesize() is a bit more reliable, it's easier to deal with architecture differences for the sizeof struct vrt_blob. For a much more reliable failure check, it now looks at logs. There may also have been a time when depending on the error we trigger we could fail with a 500 or a 503, this is no longer the case. For the nitty-gritty of the new test case, there are some comments to hopefully help (at least my future self) decipher this beast. This new test case remains stable even with the changes from #3123.
-
- 13 Nov, 2019 17 commits
-
-
Dridi Boukelmoune authored
And start adding some coverage, certainly not exhaustive.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Nils Goroll authored
-
Nils Goroll authored
added by @lkarsten as suggested by @Driri in #3122
-
Lasse Karstensen authored
This adds another vim-style key binding to varnishstat. Couldn't find any good way to extend u00008.vtc to test it. The cursor is always at column 22 and page-downing to the bottom will break the test case when we add another counter.
-
Dridi Boukelmoune authored
-
Nils Goroll authored
-
Nils Goroll authored
This fixes #3003 properly restore tests/r02219.vtc to the same headroom as before we need additional workspace for the priv_top which now always gets initialized (32 bytes on my machine)
-
Nils Goroll authored
Also fix some errors in vcl0 handling: - Only the top request may release vcl0 because it owns it - because we can re-embark for ESI, we can not assert that vcl0 is NULL in CNT_Embark() passes tests/r02849.vtc again. still fails r03003.vtc, which will get fixed in a follow up commit Fixes #3019 with test case by @Dridi
-
Nils Goroll authored
Dynamically creating it through Req_MakeTop() would further complicate rollbacks. The memory overhead is basically identical to embedding struct reqtop into struct req, except that, for ESI, we have the (struct req).top point to the top request's struct reqtop. With this commit, tests/r02849.vtc and tests/r03003.vtc are failing as excpected. While this may impose issues with git bisect, I still think that this extra commit helps clarity.
-
Nils Goroll authored
This reverts commit d6799345. We will use struct reqtop for vcl0 and PRIV_TOP in follow-up commits.
-
Nils Goroll authored
This reverts commit d6d34160 which reverted 86af5ce0. The regression documented in #3003 will be solved differently in follow-up commits. r03003.vtc added in d6d34160 is kept
-
Nils Goroll authored
-
Nils Goroll authored
I noticed that the stream 0 header accounting changes with len == 0 VDP bytes, which seems useless.
-
- 12 Nov, 2019 1 commit
-
-
Poul-Henning Kamp authored
-
- 11 Nov, 2019 4 commits
-
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-