Use this skill to investigate failed end-to-end tests in GitHub Actions. It downloads the run’s log artifacts, checks OAP and other component logs for errors, and summarizes the likely root cause, including failures in standalone test tools.
Download and inspect CI e2e test logs from GitHub Actions artifacts. Use when investigating e2e test failures in CI.
Run score Not tested
See how to installProvide a GitHub Actions run ID or URL to retrieve and extract its E2E test log artifacts. The skill checks OAP server logs and logs from BanyanDB, the UI, and other components for errors and exceptions, then organizes the findings around the test failure. If OAP logs show no problem, it also checks the failed test step and separate processes such as the profile exporter.
Use it when an E2E test fails in GitHub Actions and you want to narrow down the cause without gathering the logs by hand. It can help compare logs from multiple Pods, including initialization Pods, and trace failures in test processes that run separately from the server.
Log retrieval uses gh, and downloading and extracting artifacts requires unzip.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Download test log artifacts from a GitHub Actions CI run and inspect them for errors.
Find the artifact: Use gh api to list artifacts for the given CI run:
gh api repos/apache/skywalking/actions/runs/<RUN_ID>/artifacts --jq '.artifacts[] | {id: .id, name: .name}'
Download and extract: Download the artifact zip and extract it:
cd /tmp && rm -rf e2e-debug-logs && mkdir e2e-debug-logs && cd e2e-debug-logs
gh api repos/apache/skywalking/actions/artifacts/<ARTIFACT_ID>/zip > artifact.zip
unzip -o artifact.zip
Inspect OAP logs: Look for errors in the OAP server logs:
# Find OAP log files
find /tmp/e2e-debug-logs -name "skywalking-oap-*.log" -o -name "oap.log"
# Check for errors
grep -E "ERROR|Exception|FATAL|CannotCompileException" <log_file> | head -30
Inspect other component logs: Check BanyanDB, UI, and other pod logs as needed.
Report findings: Summarize the root cause error from the logs.
$SW_INFRA_E2E_LOG_DIRMockCoreModuleProvider. If a new service is added to CoreModule.services() but not registered in the mock, the exporter fails at startup with requiredCheck() error — but the OAP logs will show no errors (OAP is fine, the exporter subprocess is what fails). Check the test step that runs profile_exporter.sh.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Validate SkyWalking OAP changes by building the backend or full project and running Javadoc and Checkstyle checks. Choose commands for a full CI-style build, a faster backend build, one check, or a single module before submitting a pull request.
Compile SkyWalking DSL scripts for MAL, OAL, LAL, or Hierarchy and save the generated .class files for inspection. Choose one DSL or generate classes for all four, then locate the output and use javap to examine bytecode.
Prepare a pull request branch by running the documented build, style, license-header, and Java import checks, then committing and pushing the changes. If the branch has no pull request yet, create one using the project template.
Check whether source files carry the required Apache 2.0 headers and whether the dependency license file matches current dependencies. Use the provided commands to fix headers or regenerate the license list, then review any changes before submitting a pull request.
Plan how to add a monitoring target or layer to SkyWalking OAP. The guide maps signals such as metrics, logs, and spans to extension points, and identifies related layer registration, UI templates, documentation, and local verification work.
Rebuild SkyWalking’s distribution and OAP Docker image after source changes, choosing a command sequence that includes the updated JARs. It also explains how to inspect the image contents before running end-to-end tests.