An error occurred during the execution of a CI/CD workflow.
Failure Details
Total Tests: 58 - Failure: 1 (skipped: 0, pending: 0) - Executed in 145s
FAILURES:
| Suite: report.json - Total tests: 58 - Failure: 1 - Executed in 145s
| | - Server Load probe test
| | | - FAIL: Check that patcher probe is red after failing a patch
Service: server-availability-manager
Date: 2026-08-17T13:36:05.746Z
Source URL: https://github.com/Jahia/server-availability-manager/actions/runs/32033991583
Dedup Key: 30c9a7fe-8987-5648-8a22-4faeeeb7a074
Details about the process or how to disable notifications is available on this confluence page .
Expand to learn more about these issues
About
This issue was created by jahia-reporter by an automated CI/CD workflow (see link above).
Using a "Dedup key", the tool will identify similar failure for a particular service.
The following logic is present:
-
A successful run for a service will close ALL open issues for that service for ALL dedup keys
-
Updates are not posted if the status did not change (i.e. two subsequent failures only results in one single issue or single comment).
-
A previously closed issues will be re-opened if it starts failing again.
The Dedup key is generated from the list of failed test cases sorted alphabetically.
An error occurred during the execution of a CI/CD workflow.
Failure Details
Service: server-availability-manager
Date: 2026-08-17T13:36:05.746Z
Source URL: https://github.com/Jahia/server-availability-manager/actions/runs/32033991583
Dedup Key: 30c9a7fe-8987-5648-8a22-4faeeeb7a074
Details about the process or how to disable notifications is available on this confluence page .
Expand to learn more about these issues
About
This issue was created by jahia-reporter by an automated CI/CD workflow (see link above).
Using a "Dedup key", the tool will identify similar failure for a particular service.
The following logic is present:
A successful run for a service will close ALL open issues for that service for ALL dedup keys
Updates are not posted if the status did not change (i.e. two subsequent failures only results in one single issue or single comment).
A previously closed issues will be re-opened if it starts failing again.
The Dedup key is generated from the list of failed test cases sorted alphabetically.