Status Update
No update yet.
Comments
ke...@gmail.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%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:
aj...@google.com
Tested the issue on latest chrome version #131.0.6778.265 using windows 11 as per steps in
Steps to reproduce:
=================
1.Launch Chrome
2. Set up a multi-monitor system with two monitors horizontally, one with 100% at left, one with 200% at right.
3.place the window on the left monitor and drag it to the middle of the screen
4.Hover the pointer on the window border, caption button, , toggle buttons.
observed that "hit-tests working normally on multi monitors"
@Reporter: Could you please
1) Review the attached screencast and let us know if we missed anything from our end.
2) Provide an screencast for better understanding/triaging the issue.
Attaching screencast for reference
Thanks..!
Steps to reproduce:
=================
1.Launch Chrome
2. Set up a multi-monitor system with two monitors horizontally, one with 100% at left, one with 200% at right.
3.place the window on the left monitor and drag it to the middle of the screen
4.Hover the pointer on the window border, caption button, , toggle buttons.
observed that "hit-tests working normally on multi monitors"
@Reporter: Could you please
1) Review the attached screencast and let us know if we missed anything from our end.
2) Provide an screencast for better understanding/triaging the issue.
Attaching screencast for reference
Thanks..!
Description
NOTE: Changing the template (or component which causes a template change) may change the access level this bug defaults to and it may no longer be confidential.
Chrome Version: 131.0.6778.265 OS: Windows 11 Version 23H2 (Build 22631.4460)
What steps will reproduce the problem?
(1) Set up a multi-monitor system with two monitors horizontally, one with 100% at left, one with 200% at right.
(2) place the window on the left monitor, hold the right most side of the title bar (near the caption button), and slowly drag to the middle of the two screens, make the window occupy a slightly larger proportion of the right screen, release the window before window DPI changes.
(3) test the hit test like hovering your mouse on the window border, caption button, etc.
What is the expected result?
hit test in all place should work properly
What happens instead?
hit test did not work in some area, usually there are problems with the right and bottom borders
Please use hotlists and text to provide additional information.
If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py ) to help us identify the root cause and more rapidly triage the issue.
For graphics-related bugs, please copy/paste the contents of the about://gpu page at the end of this report.
Upload Chrome variations which can help us investigate this issue. 1 Open Chrome. Go to chrome://version/?show-variations-cmd 2 Notice that there is a "Command-line variations" section(you might need to scroll down the page). Copy and save the value of the section to a txt file like variations.txt. 3 Upload the file to this bug as an attachment.