All skills
openshift avatar

/e2e-analyze

@526b5e5 official
by openshiftopenshift/hypershift543 stars
576

Analyze test errors

  • 1 file
  • 1.2 KB
  • Updated 2 months ago
  • GitHub

Use this Skill: https://skilld.dev/gh/openshift/hypershift/e2e-analyze

This session only. Nothing lands on disk.

SKILL.md

≈8 tokens always: the name and description. ≈292 when used: this file.

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:
    Error: {Error message here}
    Summary: {Failure analysis here}
    Evidence: {Evidence here}
    Additional evidence: {Additional evidence here}

Source: SKILL.md on GitHub

No third-party reports yet.

Signed by skilld at 526b5e5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for openshift/hypershift/e2e-analyze