Cairn
NousResearch/hermes-agent

Classify Windows NTSTATUS loader exits as crashes in test runner

Cluster 137198 · other. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

One bug report and two pull requests concern the test runner labeling Windows loader-failure exit codes (such as 0xC0000142 and 0xc000012d) as "no tests ran (collection/import error)" rather than as a crash. The pull requests propose classifying these NTSTATUS exits as CRASHED or interpreter crashes.

Open issues1

  • Issue#137198[Bug]: test runner files Windows loader-failure exits (0xC0000142/0xc000012d) as "no tests ran (collection/import error)" instead of CRASHED

Open PRs2

  • PR#137233fix(tests): file Windows NTSTATUS exits as CRASHED, not "no tests ran"
  • PR#137764fix(runner): classify Windows NTSTATUS exits as interpreter crashes
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.67: 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

Subsystem
other
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/137198.json
cluster/137198.md