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
3f67c2d3
Commit
3f67c2d3
authored
Jul 10, 2023
by
Dridi Boukelmoune
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
vtc: Disable c124
parent
f337b2c9
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
2 deletions
+8
-2
c00124.vtc.disabled
bin/varnishtest/tests/c00124.vtc.disabled
+8
-2
No files found.
bin/varnishtest/tests/c00124.vtc
→
bin/varnishtest/tests/c00124.vtc
.disabled
View file @
3f67c2d3
varnishtest "rushed task queued"
# this does not work reliably because the acceptor task may
# be queued during the child startup if not all threads are
# created
# thread reserve mitigation barrier
barrier b0 sock 2
...
...
@@ -61,12 +65,14 @@ varnish v1 -expect threads == 5
client c1 {
txreq -hdr "Cookie: foo" -hdr "server: s1"
rxresp
expect resp.status == 200
} -start
# 2 threads
client c2 {
txreq -hdr "server: s2"
rxresp
expect resp.status == 200
} -start
# ensure c1 and c2 fetch tasks are started
...
...
@@ -84,11 +90,11 @@ varnish v1 -expect sess_dropped == 0
varnish v1 -expect sess_queued == 0
# At this point, we are thread-starved and c3 below will steal the
# acceptor thread. It will be queued before the acceptor task queues
# itself with a lower priority.
# acceptor thread that will queue itself.
client c3 {
txreq
rxresp
expect resp.status == 200
} -start
logexpect l1 -wait
...
...
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