kevinveenbirkenbachandClaude Opus 5 70d7ddf5fc test(cache): assert the guarded call writes nothing, not that the cache is empty ...

test_the_guarded_payload_never_reaches_the_main_cache compared
_MERGED_APPLICATIONS_CACHE against {}, which couples it to everything that
ran before it in the same xdist worker even though setUp resets the cache.
It failed once inside `make quality`, whose four test targets run in
parallel, and passed in four runs since: isolated, whole file, `make
test-unit` and a full unit-plus-lint sweep.

Recording the key set before the call and comparing it afterwards states
what the test name claims and stays true whatever else populated the cache.
A real write by the guarded path still fails it.

Why the cache held an entry in that one run is unexplained. utils/cache has
no on-disk layer and utils/cache/applications.py starts no thread the
thread-local render guard could miss, so neither cross-process nor
cross-thread leakage accounts for it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-26 04:56:44 +02:00

..

users

fix(users): default the email of users declared only in the inventory

2026-09-22 15:56:00 +02:00

__init__.py

…

test_applications.py

test(cache): assert the guarded call writes nothing, not that the cache is empty

2026-09-26 04:56:44 +02:00

test_base.py

fix(cache): key the applications SPOT by the groups its payload reads

2026-09-17 21:12:42 +02:00

test_data.py

fix(cache): key the applications SPOT by the groups its payload reads

2026-09-17 21:12:42 +02:00

test_domains.py

…

test_files.py

fix(lint): stop the project walk at the build artefact tree

2026-09-24 22:00:51 +02:00

test_variants.py

…

test_yaml.py

…