- 28 May, 2021 7 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
A wrong WRONG doesn't make it right for SunCC.
-
Dridi Boukelmoune authored
To cut down synchronization needs for the very beginning of a session.
-
Dridi Boukelmoune authored
The tunnel acts like a client and a server and forwards bytes between two parties. It can then pause in the middle of a session and control how much data can go in either direction. Combined with barriers it can be used to trigger socket timeouts, possibly in the middle of protocol frames. A tunnel works with two threads: one to execute its spec and one to poll both parties and transfer data accordingly. The two threads synchronize via basic pthread primitives and follow a very simplistic state machine: ACCEPT -> RUNNING <-> PAUSED -> SPEC DONE -> POLL DONE -> STOPPED Despite being simplistic, the coordination of two threads would likely complicate the implementation of a `-repeat` action, but it is still possible to `start` a tunnel again as shown in the c106 test case that exercises basic coverage involving a varnish instance. Usage is documented in the vtc(7) manual.
-
Poul-Henning Kamp authored
-
- 26 May, 2021 2 commits
-
-
Johan Hendriks authored
Small typo
-
Dridi Boukelmoune authored
Ever since my system upgraded haproxy to 2.3.10 this test has consistently timed out. While that would be a breaking change involving the independent vtest project too, I think the VTC syslog spec would work better with something like: expect skip facility.level regex Where skip could be uint, * or ? similar to how logexpect works, and both facility and level could also be * to be non-specific. For now, let's hope this does not break the test suite for anyone else.
-
- 24 May, 2021 3 commits
-
-
Guillaume Quintard authored
under pressure, tests get slow and time out
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 21 May, 2021 4 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 20 May, 2021 1 commit
-
-
Poul-Henning Kamp authored
-
- 19 May, 2021 9 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Considerable work went into RFC8941 to establish that there is neither a nead nor a reason to support parsing scientific notation in HTTP header context.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 18 May, 2021 1 commit
-
-
Dridi Boukelmoune authored
Refs 9aa7fae2
-
- 17 May, 2021 6 commits
-
-
Dridi Boukelmoune authored
This is to avoid a confusion between cancelling a fetch from a client transaction and abandoning a fetch from a backend transaction.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Spotted by: @dridi
-
Poul-Henning Kamp authored
Fixes: #3251
-
Poul-Henning Kamp authored
Prep work for #3251
-
- 12 May, 2021 1 commit
-
-
Poul-Henning Kamp authored
-
- 11 May, 2021 3 commits
-
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
They are currently triggering on readline/libedit includes, preventing the sanitizer job to fail for a good reason. We still have developer warnings as part of our circle and vtest ci. Better diff with the --word-diff option.
-
Dridi Boukelmoune authored
There's no convenient way to parameterize configure arguments to pass them on to distcheck's configure step. We already run distcheck on circle ci and vtest, so it's simpler to simply run the check target. Refs 26e92d15
-
- 10 May, 2021 3 commits
-
-
Poul-Henning Kamp authored
The actual agorithm was found with `gperf` but its output is not directly usable and include/tbl/http_headers.h change so infrequently that this step is not automated. (Asserts protect against overlooking this step if new headers are added to the table.)
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-