Menu
Suite of tools to fetch TOPSAIL CI logs and artifacts for test troubleshooting
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | topsail-ci |
| description | Suite of tools to fetch TOPSAIL CI logs and artifacts for test troubleshooting |
To troubleshoot TOPSAIL CI runs, you need to download the CI logs, and if necessary to investigate further, download the CI artifacts to better understand what happened.
To download the CI logs, you need to ask the user the PR number (PR_NUMBER).
usually, there's only one test TEST_NAME
BUILD_IDSTEP_NAME are the setup of the infrastructure (the jump-ci):lock-clusterprepare-jump-ciunlock-clusterIf they fail, it's an infra-structure failure. This should be clearly specified to the user, but she'll nonetheless need help to know which part failed. Their artifacts directory is at this location:
pre-cleanuppreparetestpost-cleanup (optional)Their artifacts are at this location:
Notice the trailing test-artifacts directory name. This directory is created by the Jump-CI. Anything inside it is the actual test artifacts. Anything at the same level is the artifacts of the Jump-CI infrastructure.
run.log file shows the full trace of thethis file might be long and hard to grasp (for the user).
FAILURES file, if present, gives an indication of what failed:DIRECTORY of artifacts:gsutil -m cp -r gs://test-platform-results/pr-logs/pull/openshift-psap_topsail/PR_NUMBER/TEST_NAME/BUILD_ID/artifacts/jump-ci/STEP_NAME/artifacts/test-artifacts/DIRECTORY .
(the command is also shown at the bottom of the directory listing).