flaky-smoke-tests

Diagnose intermittent VS Code Electron smoke-test failures from Azure DevOps pipeline logs.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill flaky-smoke-tests-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flaky-smoke-tests
Source: https://github.com/Tyrizx/Tyrizx/tree/main/.github/skills/flaky-smoke-tests
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill flaky-smoke-tests-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Intermittent Electron smoke-test failures in the VS Code Flaky Smoke Tests pipeline (Azure DevOps definition 700) are hard to investigate because iteration tasks report succeededWithIssues, logs are shared across iterations, and artifacts can be overwritten or missing. This Skill provides a systematic procedure to locate the failed iteration, retrieve the right logs, and trace the root cause. ## Core Features & Use Cases - Failed Iteration Discovery: Query the build timeline with Azure CLI to find iteration tasks that failed or returned succeededWithIssues, and download their exact task logs. - Artifact Correlation: Download per-platform logs and crash-dump artifacts, then correlate the failed task's time range with the cumulative smoke-test-runner.log to isolate the failing interval. - Root Cause Tracing: Follow the gesture/dispatch/request/rendering chain, use git blame and git log to identify the introducing commit, and queue focused validation runs with custom iteration counts. - Use Case: A scheduled definition-700 run shows a red macOS iteration. Use this Skill to pull the timeline, download the task log and logs-macos-arm64 artifact, identify the racy commit, and queue a six-iteration validation run on your fix branch. ## Quick Start Diagnose the failed smoke-test iterations in Azure DevOps build 12345 from the Monaco project's flaky smoke tests pipeline.

Frequently Asked Questions about flaky-smoke-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find failed smoke test iterations in an Azure DevOps build?▼

Download the build timeline using az devops invoke with the build timeline resource, then filter records whose names contain Smoke test iteration. Treat tasks with result succeededWithIssues, failed, or error issues as failed iterations and record their task ID, log ID, and time range.

How to download Azure Pipelines task logs with Azure CLI?▼

Use az devops invoke with the build logs resource, passing the buildId and the timeline record's logId, and write the response to a file. The JSON response contains a value array of log lines that you convert to plain text with jq or PowerShell.

Why does a smoke test iteration show succeeded but still fail?▼

Iteration tasks use continueOnError set to true, so a failed iteration reports succeededWithIssues and later iterations still run. You must inspect every iteration task individually rather than inferring health from the overall build or job result.

Why is the smoke test logs artifact missing after a canceled run?▼

Canceling a platform job can skip the artifact publish steps entirely, even when failed iteration task logs exist. An absent platform artifact after cancellation is expected and does not mean the artifact name was wrong.

How do I queue a focused validation run for pipeline definition 700?▼

Use az pipelines run with the branch, commit ID, and an iterations parameter such as iterations=[1,2,3,4,5,6], enabling only the relevant platform build flags. Six iterations give a quick sample; use the default 20 for rare failures.