Eric Eastwood 30cb7831df Fix test that assumes reactor time starts at 0 ...

It no longer starts at 0 because we `self.reactor.advance(...)`
waiting for the background updates to finish.

2026-07-29 00:24:15 -05:00

..

__init__.py

Wrap register_device coroutine in an ensureDeferred (#7684)

2020-06-16 10:13:59 +01:00

test_account_data_manager.py

Introduce Clock.call_when_running(...) to include logcontext by default (#18944)

2025-09-22 10:27:59 -05:00

test_api.py

Fix test that assumes reactor time starts at 0

2026-07-29 00:24:15 -05:00

test_event_unsigned_addition.py

Introduce Clock.call_when_running(...) to include logcontext by default (#18944)

2025-09-22 10:27:59 -05:00

test_spamchecker.py

Introduce spam_checker_spammy internal event metadata. (#19453)

2026-04-15 16:53:23 +01:00