check-upstream-flake

Query Chromium's LUCI Analysis database for upstream test flakiness statistics.

3.5k|1.4k|Updated Nov 10, 2017

Search Tags:#testing #debugging #ci #chromium #flakiness #luci

Ready to run

npx skills add https://github.com/brave/brave-core --skill check-upstream-flake-brave

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-upstream-flake
Source: https://github.com/brave/brave-core/tree/main/.claude/skills/check-upstream-flake
Command: npx skills add https://github.com/brave/brave-core --skill check-upstream-flake-brave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly determine if a failing test is due to an intermittent issue in the upstream Chromium project, preventing wasted effort on Brave-specific fixes.

Core Features & Use Cases

Flakiness Analysis: Queries the Chromium LUCI Analysis database to check historical test stability.
Verdict & Recommendation: Provides a clear verdict (e.g., "Known upstream flake", "Stable upstream") and actionable advice for filter file decisions.
Use Case: When a test fails in your CI run, use this Skill to check if it's a known upstream flake before investigating Brave's codebase.

Quick Start

Check if the test 'WebUIURLLoaderFactoryTest.RangeRequest' is a known upstream flake.

Frequently Asked Questions about check-upstream-flake

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

FAQPage Schema

How do I check if a failing test is an upstream Chromium flake?▼

To check for an upstream flake, query the Chromium LUCI Analysis database with the failing test name. The Skill returns historical flakiness statistics and a clear verdict indicating whether the failure is a known upstream issue.

What is LUCI Analysis flakiness data used for in CI debugging?▼

LUCI Analysis flakiness data is used to identify intermittent test failures originating from the upstream Chromium project. It helps developers avoid wasting effort investigating Brave-specific codebases when a test is historically unstable upstream.

How do I decide whether to add a flaky test to a filter file?▼

To decide on filter file actions, review the flakiness verdict and recommendation provided by the LUCI Analysis query. If the test is confirmed as a known upstream flake, the Skill advises on appropriate filter file decisions to suppress the failure.

Does this tool check LUCI flakiness for Brave-specific tests or upstream tests?▼

This tool checks LUCI flakiness specifically for upstream Chromium tests. It determines if your failing test is a known issue in the Chromium project to prevent unnecessary debugging of Brave-specific code.

What should I do if a test is stable upstream but failing in my CI run?▼

If a test is reported as stable upstream but failing in your CI run, the Skill will indicate it is not a known upstream flake. You should then investigate your Brave-specific codebase as the failure is likely caused by local changes.