Assigned
Status Update
No update yet.
Comments
bi...@google.com
This bug been identified as part of Chrome's flake reduction initiative. Resolution of this issue is critical because it has a large impact on the stability of Chrome CI/CQ. Resolving these issues will be essential to meet Chrome’s flake reduction goals.
This bug has led to a large number of gardened builds failing in the last 7 days. List of gardened build failures caused by this cluster can be viewed at:
https://data.corp.google.com/sites/chrome_generic_flakiness_dashboard_datasite/build_failures/?av=rpqxzw:ktu56&fb=is_sheriff_or_cq_builder:eq:true&f=cluster_name:in:b%2F400246327
or in LUCI Analysis and grouped by builders:
https://luci-milo.appspot.com/ui/tests/p/chromium/rules/5e4a5afb6d8413702aefbecb5ccb12b7?tab=recent-failures&filterToMetric=builds-failed-due-to-flaky-tests&groupBy=builder&orderBy=invocationFailures
Please consider the following strategies to mitigate the impact from this issue which are rated in order of resolution preference:
1. Resolve the underlying test issue.
2. Move the flaky test from Critical Builders to FYI Builder
3. Disable test (least desirable as it reduces test coverage) and add a Test-Disabled label to this issue. The disabled tests might continue running in reviver builders (go/test-reviver), see config [1] for a list of supported builders.
http://go/resolve-chrome-top-flakes provides more information on the tools available for resolving flaky tests.
When investigating this failure, you may identify this bug is too broad (encompasses multiple different issues) or too narrow (only captures one part of a larger issue). If this applies, you can combine issues[2] or split issues[3].
Links:
[1]https://source.chromium.org/chromium/chromium/src/+/main:infra/config/subprojects/reviver/reviver.star
[2]https://luci-analysis.appspot.com/help#combining-issues
[3]https://luci-analysis.appspot.com/help#splitting-issues
Why LUCI Analysis posted this comment:https://luci-milo.appspot.com/ui/tests/help#policy-activated (Policy ID: builds-failed-due-to-flaky-tests)
This bug has led to a large number of gardened builds failing in the last 7 days. List of gardened build failures caused by this cluster can be viewed at:
or in LUCI Analysis and grouped by builders:
Please consider the following strategies to mitigate the impact from this issue which are rated in order of resolution preference:
1. Resolve the underlying test issue.
2. Move the flaky test from Critical Builders to FYI Builder
3. Disable test (least desirable as it reduces test coverage) and add a Test-Disabled label to this issue. The disabled tests might continue running in reviver builders (go/test-reviver), see config [1] for a list of supported builders.
When investigating this failure, you may identify this bug is too broad (encompasses multiple different issues) or too narrow (only captures one part of a larger issue). If this applies, you can combine issues[2] or split issues[3].
Links:
[1]
[2]
[3]
Why LUCI Analysis posted this comment:
dp...@chromium.org
bo...@google.com
bo...@chromium.org
ap...@google.com
Project: chromium/src
Branch: main
Author: David Bokan <
Link:
Move glic shortcut tests to interactive ui tests
Expand for full commit details
Move glic shortcut tests to interactive ui tests
The shortcut edit control works by setting focus on an inner input
element. If the test window loses focus, 'focus' events aren't fired
so this doesn't work. Interactive tests focus the test window before
starting.
Bug: 400246327
Change-Id: Ie598f04a827747138209e6b1a46621b11e65134c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6317916
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1427953}
Files:
- M
chrome/test/data/webui/settings/BUILD.gn - A
chrome/test/data/webui/settings/glic_page_focus_test.ts - M
chrome/test/data/webui/settings/glic_page_test.ts - M
chrome/test/data/webui/settings/settings_focus_test.cc
Hash: f8e675126b16013c78fc30d5f71a180dd29e5415
Date: Tue Mar 04 13:25:57 2025
os...@google.com
The test continues to fail on the Builder: mac-rel-ready
Reopening the bug and disabling the test on Mac
ap...@google.com
Project: chromium/src
Branch: main
Author: Osama Fathy <
Link:
[Gardening] Disable SettingsGlicPageFocusTest.GlicPageFocus test
Expand for full commit details
[Gardening] Disable SettingsGlicPageFocusTest.GlicPageFocus test
Bug: 400246327
Change-Id: I4f04c98c3875405bd40512f58b26d3851895c10b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6330161
Owners-Override: Osama Fathy <osamafathy@google.com>
Reviewed-by: Bohdan Tyshchenko <bohdanty@google.com>
Commit-Queue: Osama Fathy <osamafathy@google.com>
Cr-Commit-Position: refs/heads/main@{#1428837}
Files:
- M
chrome/test/data/webui/settings/settings_focus_test.cc
Hash: f45b145044ca1998a005e6bce3a7d24e36ce1327
Date: Thu Mar 06 04:42:10 2025
Description
web_ui_mocha_browser_test.cc(152): Value of: RunTestOnWebContents(web_contents, file, trigger, skip_test_loader)\n Actual: false (Mocha test failures detected in file: settings/glic_page_test.js, triggered by 'mocha.run()')\nExpected: true
The following test(s) were observed to have matching failures at this time (at most five examples listed):
- ninja://chrome/test:browser_tests/SettingsGlicPageTest.GlicSettingsPage
These test failures are causing problem(s) which require your attention, including:
- many gardened builders are failing
See current problems, failure examples and more in LUCI Analysis at:
How to action this bug:
Provide feedback:
Was this bug filed in the wrong component? See: