NousResearch/hermes-agent

Kanban stress/chaos scripts CI execution gap

Cluster 93135. Data as of

Nothing open on GitHub. Fix merged in #93379 on 24 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #93379. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #93379. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members address the discovery that kanban stress and chaos scripts were never actually executed by pytest or CI, with proposals to either wire them into a nightly workflow or remove them entirely.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #93379 chore(tests): remove the never-executed kanban stress/chaos suite (#93135)

    merged to main

    files: tests/stress/README.md, tests/stress/_fake_worker.py, tests/stress/conftest.py, tests/stress/test_atypical_scenarios.py, tests/stress/test_benchmarks.py, tests/stress/test_concurrency.py, tests/stress/test_concurrency_mixed.py, tests/stress/test_concurrency_parent_gate.py, tests/stress/test_concurrency_reclaim_race.py, tests/stress/test_property_fuzzing.py, tests/stress/test_subprocess_e2e.py

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #93210 ci(stress): run standalone kernel stress scripts · superseded by another PR → #93135, #93136, #93137
  • #93358 ci(stress): kanban stress/chaos scripts actually execute — nightly workflow + honest conftest/README (#93135) · other → #93135
Closed issues · 1
  • Closed#93135Kanban stress and chaos scripts are never executed by pytest or CI
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#93379
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Aug 2026

For your agent

The same facts, typed.