hermes-agent/tests/plugins/memory
Kyzcreig 9c28600e77 test: prove concurrency with barriers/witnesses instead of wall-clock bounds
Replace OS-scheduler-dependent elapsed-time ceilings with deterministic
concurrency proofs in three tests:

- test_context_refs_concurrent: asyncio.Barrier rendezvous — all 3 URL
  fetches must be in flight simultaneously before any returns.
- test_memory_boundary_commit: positive non-blocking witness — the
  provider call list must still be empty when the async commit returns.
- test_mem0_v3 slow-prefetch: threading.Event park/release — prefetch
  must return while the backend search is still parked.

The tests/tools/test_mcp_tool.py hunk from the original PR is dropped:
main no longer carries the 'elapsed < 2.5' assertion it targeted
(superseded by a delay-relative bound).

Salvaged from #71913.
2026-07-29 21:30:53 -07:00
..
__init__.py
test_byterover_provider.py
test_config_schema.py
test_hindsight_config_schema.py
test_hindsight_provider.py fix(tests): forward Windows location vars through the hermetic runner; patch Path.home() in hindsight _clean_env 2026-07-29 18:55:10 -07:00
test_holographic_auto_extract.py
test_holographic_retrieval.py
test_holographic_shutdown_closes_db.py
test_holographic_store.py
test_honcho_config_schema.py
test_mem0_backend.py
test_mem0_providers.py
test_mem0_setup.py
test_mem0_v3.py test: prove concurrency with barriers/witnesses instead of wall-clock bounds 2026-07-29 21:30:53 -07:00
test_memory_lazy_install.py
test_openviking_provider.py
test_openviking_shutdown.py
test_retaindb_provider.py
test_supermemory_provider.py