e2e-analyze
Analyze test errors
Informations de source
- Dépôt
- openshift/hypershift
- Dernière activité de la source
- 12 août 2026 à 13:51
- Langue détectée de SKILL.md
- anglais
- Étoiles
- 546
- Forks
- 578
Options d'installation
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Vérifiez les fichiers source
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Affichage de SKILL.md
SKILL.md
Instructions source · Aperçu en lecture seule- name
- e2e-analyze
- description
- Analyze test errors
# General instructions
- Validate that "$3" is an existing directory; fail if it is not. Do NOT create the directory.
- Extract {BUILD_NUMBER} from "$1" by matching a 10–20 digit sequence; fail if none is found.
- Use the extracted number as {BUILD_NUMBER}.
- Use curl to download the file build-log.txt under "$1". Only allow HTTPS URLs (reject HTTP).
- When fetching, use: `curl -fsSL --max-time 20 --retry 3 --retry-connrefused --proto '=https' --max-filesize 100M "${1}/build-log.txt"`.
- The build-log.txt file contains e2e failures, store the artifacts related to failure "$2" under directory specified by "$3" to determine a possible root cause for the failure.
- Use the "gcloud storage" command to fetch given artifacts under "$3" and make sure to use {BUILD_NUMBER} in URLs.
- Provide evidence for the failure.
- Try to find additional evidence. For example, in logs and events.
- Do not delete downloaded artifacts during the cleanup phase.
# Output format
- The output should be formatted as:
```text
Error: {Error message here}
Summary: {Failure analysis here}
Evidence: {Evidence here}
Additional evidence: {Additional evidence here}
```
Voir sur GitHub