skyline-nightlytests
Use this skill when looking at nightly test results or investigating test failures.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Skyline Nightly Test Analysis
Full documentation: ai/docs/mcp/nightly-tests.md
MCP Tools (Quick Reference)
| Tool | Purpose |
|---|---|
get_daily_test_summary(report_date) |
Daily report for all 6 folders → ai/.tmp/ |
save_test_failure_history(test_name, start_date, container_path) |
Stack trace pattern analysis → ai/.tmp/ |
save_run_log(run_id) |
Full test log for grep/search → ai/.tmp/ |
get_run_failures(run_id) |
Stack traces for a specific run |
get_run_leaks(run_id) |
Leak details for a specific run |
Test Folders
| Folder | Duration | Branch |
|---|---|---|
| Nightly x64 | 540 min | master (default) |
| Performance Tests | 720 min | master |
| Release Branch | 540 min | release |
| Release Branch Performance Tests | 720 min | release |
| Integration | 540 min | assigned |
| Integration with Perf Tests | 720 min | assigned |
Typical Workflow
-
Daily review:
get_daily_test_summary("2025-12-15")→ read report -
Pattern analysis: If test failed on multiple machines, use
save_test_failure_historyto check if same root cause -
Deep dive: Use
save_run_logwhen stack traces aren't sufficient
Anomaly Detection
- Short duration (< expected) = crash or premature termination
- Full duration + low test count = hang
- Stddev-based: 3σ/4σ from trained mean flags anomalies
For server-side queries, examples, and detailed workflows, see ai/docs/mcp/nightly-tests.md.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!