bstein/bstein-dev-home
1
0
Fork 0
Code Issues 800 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[hermes] bstein-dev-home #571: undiagnosed #804

New Issue
Open
opened 2026-09-30 21:58:37 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-30 21:58:37 +00:00
Copy Link

Hermes auto-triage classified incident bstein-dev-home/571 as undiagnosed (confidence n/a); first failed gate: unknown.

Why a human is needed

hermes_run_failed

Ariadne did not authorize automated remediation: hermes_run_failed.

Evidence

The earliest failure region of the build console:

21:29:56.203 INFO  Sensor JaCoCo XML Report Importer [jacoco] (done) | time=9ms
21:29:56.203 INFO  Sensor IaC CloudFormation Sensor [iac]
21:29:56.566 INFO  0 source files to be analyzed
21:29:56.706 INFO  0/0 source files have been analyzed
21:29:56.708 INFO  Sensor IaC CloudFormation Sensor [iac] (done) | time=504ms
21:29:56.708 INFO  Sensor IaC Kubernetes Sensor [iac]
21:29:56.901 INFO  0 source files to be analyzed
21:29:57.068 INFO  0/0 source files have been analyzed
21:29:57.068 INFO  Sensor IaC Kubernetes Sensor [iac] (done) | time=360ms
21:29:57.069 INFO  Sensor JavaScript analysis [javascript]
21:30:11.836 ERROR Error when running: 'node -v'. Is Node.js available during analysis?
org.sonarsource.nodejs.NodeCommandException: Error when running: 'node -v'. Is Node.js available during analysis?
	at org.sonarsource.nodejs.NodeCommand.start(NodeCommand.java:79)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.getVersion(NodeCommandBuilderImpl.java:203)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.checkNodeCompatibility(NodeCommandBuilderImpl.java:169)
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.build(NodeCommandBuilderImpl.java:143)
	at org.sonar.plugins.javascript
... (truncated; the full log is in the linked build)

Links

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

Hermes auto-triage classified incident `bstein-dev-home/571` as **undiagnosed** (confidence n/a); first failed gate: `unknown`. ## Why a human is needed hermes_run_failed Ariadne did not authorize automated remediation: `hermes_run_failed`. ## Evidence The earliest failure region of the build console: ``` 21:29:56.203 INFO Sensor JaCoCo XML Report Importer [jacoco] (done) | time=9ms 21:29:56.203 INFO Sensor IaC CloudFormation Sensor [iac] 21:29:56.566 INFO 0 source files to be analyzed 21:29:56.706 INFO 0/0 source files have been analyzed 21:29:56.708 INFO Sensor IaC CloudFormation Sensor [iac] (done) | time=504ms 21:29:56.708 INFO Sensor IaC Kubernetes Sensor [iac] 21:29:56.901 INFO 0 source files to be analyzed 21:29:57.068 INFO 0/0 source files have been analyzed 21:29:57.068 INFO Sensor IaC Kubernetes Sensor [iac] (done) | time=360ms 21:29:57.069 INFO Sensor JavaScript analysis [javascript] 21:30:11.836 ERROR Error when running: 'node -v'. Is Node.js available during analysis? org.sonarsource.nodejs.NodeCommandException: Error when running: 'node -v'. Is Node.js available during analysis? at org.sonarsource.nodejs.NodeCommand.start(NodeCommand.java:79) at org.sonarsource.nodejs.NodeCommandBuilderImpl.getVersion(NodeCommandBuilderImpl.java:203) at org.sonarsource.nodejs.NodeCommandBuilderImpl.checkNodeCompatibility(NodeCommandBuilderImpl.java:169) at org.sonarsource.nodejs.NodeCommandBuilderImpl.build(NodeCommandBuilderImpl.java:143) at org.sonar.plugins.javascript ... (truncated; the full log is in the linked build) ``` ## Links - Failed build: https://ci.bstein.dev/job/bstein-dev-home/571/ - 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_b90e0b29ba7645e492c5ee75cc3ba34f](https://triage.bstein.dev/chat?resume=run_b90e0b29ba7645e492c5ee75cc3ba34f)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=bstein-dev-home classification=undiagnosed incident=bstein-dev-home/571 -->
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/bstein-dev-home#804
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?