Age | Commit message (Collapse) | Author |
|
|
|
Closes: #9025
|
|
|
|
|
|
|
|
|
|
Was too high due a left over from some bug hunting. 20 is enough to
check both zero sized and under/equal/above tag size.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The new benchmark test for blobs fs backend was rebased from a merge
request in which it was written using the new interface for blobs
backend. After rebase, the test was not reverted to old interface, and
was just failing bad. This commit fixes it.
|
|
|
|
First version, still missing consumer/producer model and some tweaks,
but working.
-- Related: #8809
|
|
|
|
-- Related: #8809
|
|
-- Related: #8809
|
|
|
|
Closes: #8691
|
|
|
|
Accessing _all_dbs slows down the test and open possibilites for
heisenbugs where some old leftover database can change code behavior.
-- Resolves: #9001
|
|
Closes: #9000
|
|
It was None for parallel tests and there is already a mechanism in place
for setting this URL, which avoids it being set in two different places.
|
|
|
|
|
|
When starting up a Soledad Server through the use of a fixture in tests,
a config file is created with the options needed for that test. As the
config file was being created in /etc and not being removed, this was
influencing servers started by other tests that don't use that fixture.
By always using a temporary directory in the server fixture, we make
sure that the config file is used only for that test and is removed
after the test is finished.
Closes: #8995
|
|
|
|
|
|
After we fixed the server to wait for checks before listening on ports
(201ef7a9b979f8c8efaedbe542c631944d8956f4), the TAC test started failing
randomly in our CI, probably because sometimes the server takes more
than 1 second to startup in the CI setup (docker in a vm).
This commit adds a check with retry, and so the test will retry 10 times
with an interval of 1 second before failing.
|
|
|
|
|