010011110 835caa1531 Use a separate connection for gravity writes ...

`sqlite3_busy_handler()` is a property of the connection, so arming it during a
write also let a DNS lookup on the shared connection wait. Open a connection for
the write instead, the way `gravity_updated()` already does for its read, and
leave the shared one exactly as it is.

The test now waits for the reader to signal that it holds the lock, and requires
the write to have taken measurably longer than a free one, so it cannot pass
without exercising the wait.

Signed-off-by: 010011110 <duckenheim@posteo.de>

2026-08-19 16:41:57 +02:00

..

api

…

pdns

…

01-pihole-tests.conf

…

arch_test.sh

…

bats_helper.bash

…

broken_lua_2.lp

…

broken_lua.lp

…

dnsmasq_warnings

…

dnsmasq_warnings.sh

…

dotdoh_query.py

…

dotdoh_regression.c

…

dotdoh_server.bats

…

dotdoh_shim.py

…

dotdoh.bats

…

gravity.db.sql

…

gzip_regression.c

…

hostnames.sh

…

http2_test.sh

…

pihole-FTL.db.sql

…

pihole.toml

…

run.sh

…

sqliterc

…

tar_regression.c

…

test_ca.crt

…

test_final.bats

…

test_suite.bats

Use a separate connection for gravity writes

2026-08-19 16:41:57 +02:00

test.crt

…

test.pem

…

versions

…

x509_read_key.expected

…

x509_read.expected

…

zone_update.py

…