메뉴
Checks if a Chromium test suite is barred by `ci_only = True` configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported code coverage.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | experimental-ci-only-validator |
| description | Checks if a Chromium test suite is barred by `ci_only = True` configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported code coverage. |
This skill provides a quick way to check if a test suite has been configured as
ci_only = True on the code coverage trybots.
Use this skill when:
TestSuiteMapper).If you have identified the test suite name (e.g., chrome_junit_tests), run the
quick check tool:
python3 tools/code_coverage/ci_only_validator.py <test_suite_name>
To verify the ci_only status of a test suite at a specific historical point
(e.g., the revision of a Gerrit CL), pass the --revision (or -r) flag:
python3 tools/code_coverage/ci_only_validator.py <test_suite_name> --revision <commit_hash_or_branch>
This is highly recommended for historical triaging because configurations on main might have changed since the CL was reviewed.
The tool will scan CQ coverage trybots and coverage-specific trybots generated
under infra/config/generated/builders/try/ and report their configuration for
the target test suite:
ci_only = True: The test suite is barred from executing on this trybot
by default during CQ runs. Gerrit coverage details for tests in this suite
will not be generated automatically unless the developer explicitly requests
them via a Gerrit footer.ci_only = False: The test suite is allowed to run on the trybot in CQ.Warning: Test suite ... was not found...: The test suite is not
configured to run on any coverage trybots, meaning no coverage details are
collected on CQ at all.python3 tools/code_coverage/ci_only_validator.py chrome_junit_tests
Output:
Checking test suite 'chrome_junit_tests' across 30 coverage trybots...
Trybot: android-code-coverage | Builder: chromium.coverage:android-code-coverage | ci_only = True
Trybot: android-desktop-x64-rel | Builder: chromium.android.desktop:android-desktop-x64-rel-15-tests | ci_only = False
Trybot: android-x86-code-coverage | Builder: chromium.coverage:android-x86-code-coverage | ci_only = True
Trybot: android-x86-rel | Builder: chromium.android:android-10-x86-nofieldtrial-rel | ci_only = True
This indicates that chrome_junit_tests is barred by ci_only = True in
standard CQ at HEAD.
python3 tools/code_coverage/ci_only_validator.py chrome_junit_tests --revision verify-junit-coverage
Output:
Checking test suite 'chrome_junit_tests' across 30 coverage trybots at revision verify-junit-coverage...
Trybot: android-code-coverage | Builder: chromium.coverage:android-code-coverage | ci_only = False
Trybot: android-desktop-x64-rel | Builder: chromium.android.desktop:android-desktop-x64-rel-15-tests | ci_only = False
Trybot: android-x86-code-coverage | Builder: chromium.coverage:android-x86-code-coverage | ci_only = False
Trybot: android-x86-rel | Builder: chromium.android:android-10-x86-nofieldtrial-rel | ci_only = False
This indicates that on the verify-junit-coverage branch, the ci_only
restriction has been successfully disabled.
Finds common violations of the Android accessibility API in the Clank App Java code and attempts to address them (e.g. hardcoded state change announcements, missing events, focus moving, assertive live regions, etc).
Identify and safely remove expired Chromium histograms (dead metrics/technical debt). Use this skill when a contributor asks to clean up metrics, fix code health issues related to histograms, remove obsolete code, or work on a histogram cleanup task.
Orchestrator for the "Code Health Hub" framework. Trigger only when the user refers to the Hub or asks to see "available cleanup tasks" within the Chromium technical debt reduction system.
Identify and clean up inline fully qualified Java names (FQNs) in first-party code, replacing them with standard imports.
Add missing LINT.IfChange(...) / LINT.ThenChange(...) guards to enums in C++/Java and XML to keep them in sync. Trigger this skill ONLY when a contributor explicitly asks to add lint guards or synchronize enums using LINT guards.
Executes the phased, multi-skill code coverage debugging playbook for triaging underreported code coverage in the Gerrit Commit Queue (CQ).