bstein/ariadne
1
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[hermes] ariadne #408: pytest_test_failure #2

New Issue
Closed
opened 2026-08-06 04:44:43 +00:00 by bstein · 0 comments
bstein commented 2026-08-06 04:44:43 +00:00
Owner
Copy Link

Hermes auto-triage classified incident ariadne/408 as pytest_test_failure (confidence 0.99); first failed gate: tests (pytest: tests/test_utils.py::test_safe_error_detail_http_status_json).

Why a human is needed

This is a repository test failure in job ariadne, not a transient infrastructure signature.

Facts

  • jenkins — Jenkins job ariadne build 408 finished with result FAILURE and exit code 1. (ariadne bundle: jenkins.build_number=408, jenkins.result=FAILURE, console_tail)
  • jenkins — The earliest enforced failure evidence is the pytest failure in tests/test_utils.py::test_safe_error_detail_http_status_json: safe_error_detail returned "http 400", which did not contain the expected string "bad things". (ariadne bundle: jenkins.console_failures marker "=== FAILURES ===" at line 1949)
  • jenkins — Pytest reported 1 failed and 1163 passed tests; the subsequent tests_rc value was 1. (ariadne bundle: jenkins.console_failures marker "short test summary" at line 2035)
  • jenkins — The coverage contract passed at 100 files meeting the 95.00% threshold; the tests gate condition set gate_rc=1 because tests_rc was nonzero. (ariadne bundle: jenkins.console_failures marker "short test summary" at line 2035)
  • opensearch — Jenkins provisioning and termination records show the build agent pod was created, ran, and was terminated after the build; no infrastructure, connectivity, registry, or image-pull error is recorded in the supplied log evidence. (ariadne bundle: log_evidence.records, 2026-08-06T04:34:57.266Z through 2026-08-06T04:43:10.330Z)

Inferences

  • The test expectation and the current safe_error_detail behavior are inconsistent: the function appears to omit the HTTP response JSON errorMessage from its returned detail. The bundle does not establish whether the implementation or the test expectation should change.
  • The SonarQube and Trivy excerpts precede the pytest failure but contain setup or successful scanner-progress output, not an enforced failure.

Links

  • Failed build: https://ci.bstein.dev/job/ariadne/408/
  • Full evidence bundle and audit trail live in Ariadne at /api/admin/audit/events, event types hermes_autotriage_incident and hermes_autotriage_diagnosis.

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_3d9d4b244b8040578e354e8398c25f4b). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `ariadne/408` as **pytest_test_failure** (confidence 0.99); first failed gate: `tests (pytest: tests/test_utils.py::test_safe_error_detail_http_status_json)`. ## Why a human is needed This is a repository test failure in job ariadne, not a transient infrastructure signature. ## Facts - **jenkins** — Jenkins job ariadne build 408 finished with result FAILURE and exit code 1. (`ariadne bundle: jenkins.build_number=408, jenkins.result=FAILURE, console_tail`) - **jenkins** — The earliest enforced failure evidence is the pytest failure in tests/test_utils.py::test_safe_error_detail_http_status_json: safe_error_detail returned "http 400", which did not contain the expected string "bad things". (`ariadne bundle: jenkins.console_failures marker "=== FAILURES ===" at line 1949`) - **jenkins** — Pytest reported 1 failed and 1163 passed tests; the subsequent tests_rc value was 1. (`ariadne bundle: jenkins.console_failures marker "short test summary" at line 2035`) - **jenkins** — The coverage contract passed at 100 files meeting the 95.00% threshold; the tests gate condition set gate_rc=1 because tests_rc was nonzero. (`ariadne bundle: jenkins.console_failures marker "short test summary" at line 2035`) - **opensearch** — Jenkins provisioning and termination records show the build agent pod was created, ran, and was terminated after the build; no infrastructure, connectivity, registry, or image-pull error is recorded in the supplied log evidence. (`ariadne bundle: log_evidence.records, 2026-08-06T04:34:57.266Z through 2026-08-06T04:43:10.330Z`) ## Inferences - The test expectation and the current safe_error_detail behavior are inconsistent: the function appears to omit the HTTP response JSON errorMessage from its returned detail. The bundle does not establish whether the implementation or the test expectation should change. - The SonarQube and Trivy excerpts precede the pytest failure but contain setup or successful scanner-progress output, not an enforced failure. ## Links - Failed build: https://ci.bstein.dev/job/ariadne/408/ - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run `run_3d9d4b244b8040578e354e8398c25f4b`). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=ariadne classification=pytest_test_failure incident=ariadne/408 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bstein
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bstein/ariadne#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?