Assigned
Status Update
Comments
db...@chromium.org <db...@chromium.org> #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:
pa...@seznam.cz <pa...@seznam.cz> #3
note: I tried to do this in firefox on Android and it crashed, so it seems like it's some issue related to the file picker.
pa...@seznam.cz <pa...@seznam.cz> #4
This issue in Firefox looks like it could be the same problem. https://bugzilla.mozilla.org/show_bug.cgi?id=1887309
I've added a comment there.
I've added a comment there.
pa...@seznam.cz <pa...@seznam.cz> #5
I can no longer reproduce this issue on my phone, so it seems like this might have been fixed somewhere (maybe in One UI?)
ck...@google.com <ck...@google.com> #6
Peter & Finnur, you are both listed as owners of ui/android/java/src/org/chromium/ui/base/SelectFileDialog.java
Could one of you PTAL for further triage?
Thanks,
Android FE Gardener
Description
Steps to reproduce the problem
Use an affected Android device (Samsung S23 in my case).
EXPECTED: browser procceeds to submit the form (assuming the url is valid, which it was in my case) ACTUAL: browser fails with ERR_FAILED (or just NetworkError if the form is submitted via AJAX request)
Problem Description
If the file is picked in the specific way described above, it will fail.
Looking into more details about the file from the form data reveals that it has 0 size and the name is just a big number (without any suffix).
If I click "browse" in the bottom sheet picker and pick the file in the file manager instead, it works correctly - picks the file with timestamp name and mp4 suffix, as expected.
Summary
Picking an edited video file into input[type=file] on Android fails to submit with NetworkError
Custom Questions
Which component does this fall under?
Not sure - I don't know
Does this work in other browsers?
Not sure - I don't know
Additional Data
Category: API
Chrome Channel: Stable
Regression: N/A