Bug P2
Status Update
Comments
pa...@google.com <pa...@google.com> #2
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%2F400617105
or in LUCI Analysis and grouped by builders:
https://luci-milo.appspot.com/ui/tests/p/chromium/rules/3519deb73451d0c9b91241ccea2406fa?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:
bu...@gmail.com <bu...@gmail.com> #3
I will check the screenshot of the still-reproduced bug in c#2, all sites
in site: command are the same.
On Wed, Feb 19, 2025 at 12:26 AM <buganizer-system@google.com> wrote:
in site: command are the same.
On Wed, Feb 19, 2025 at 12:26 AM <buganizer-system@google.com> wrote:
pe...@google.com <pe...@google.com> #4
Thank you for providing more feedback. Adding the requester to the CC list.
bu...@gmail.com <bu...@gmail.com> #5
Thank you for your support! See video in c#2 of the bug.
On Sat, Feb 22, 2025 at 2:42 PM <buganizer-system@google.com> wrote:
On Sat, Feb 22, 2025 at 2:42 PM <buganizer-system@google.com> wrote:
aj...@google.com <aj...@google.com> #6
Able to reproduce the issue on the latest chrome version #133.0.6943.126 using Linux debian as per comment #1
Reproducible:
===================
Stable: 133.0.6943.126
Beta: 134.0.6998.23
Dev: 135.0.7023.0
Canary: 135.0.7034.0
Observed that "Image search results automatically views all the sites"
Note: Able to reproduce the issue in win11 and Mac also.
The issue is seen from M-122 Considering this is a non regression issue. Hence marking it as untriaged and requesting someone from the respective team to look into this for further updates.
Thanks..!
Reproducible:
===================
Stable: 133.0.6943.126
Beta: 134.0.6998.23
Dev: 135.0.7023.0
Canary: 135.0.7034.0
Observed that "Image search results automatically views all the sites"
Note: Able to reproduce the issue in win11 and Mac also.
The issue is seen from M-122 Considering this is a non regression issue. Hence marking it as untriaged and requesting someone from the respective team to look into this for further updates.
Thanks..!
bu...@gmail.com <bu...@gmail.com> #7
Thanks for the update. See video in Chrome version 133 of the
still-reproduced bug.
On Tue, Feb 25, 2025 at 2:06 AM <buganizer-system@google.com> wrote:
still-reproduced bug.
On Tue, Feb 25, 2025 at 2:06 AM <buganizer-system@google.com> wrote:
Description
if the site: command is searched.
Steps to Reproduce:
1. Go to
2. Search for site:
3. Click on "Images" to try to view on one site.
Actual Result:
Image search results automatically views all the sites.
Expected Result:
Image search results view on one site.
Additional Context:
Image search results automatically views all the sites. See video and
screenshot.