Infeasible
Status Update
Comments
gu...@xiaomi.corp-partner.google.com <gu...@xiaomi.corp-partner.google.com> #2
Device Under Test: Pixel 9
Test Suite Version: 15_r2
Build number:AP41.240823.009
==Preconditions==
run cts-on-gsi -m CtsInputMethodTest
java.util.concurrent.TimeoutException:
at android.view.inputmethod.cts.util.TestUtils.waitOnMainUntil(TestUtils.java:144)
at android.view.inputmethod.cts.util.TestUtils.waitOnMainUntil(TestUtils.java:170)
at android.view.inputmethod.cts.SpellCheckerTest.misspelled_easyCorrect(SpellCheckerTest.kt:140)
== Analysis ==
failure is due to test issue
== Mandatory Attachments ==
see attachment
Test Suite Version: 15_r2
Build number:AP41.240823.009
==Preconditions==
run cts-on-gsi -m CtsInputMethodTest
java.util.concurrent.TimeoutException:
at android.view.inputmethod.cts.util.TestUtils.waitOnMainUntil(TestUtils.java:144)
at android.view.inputmethod.cts.util.TestUtils.waitOnMainUntil(TestUtils.java:170)
at android.view.inputmethod.cts.SpellCheckerTest.misspelled_easyCorrect(SpellCheckerTest.kt:140)
== Analysis ==
failure is due to test issue
== Mandatory Attachments ==
see attachment
vi...@google.com <vi...@google.com> #3
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
gu...@xiaomi.corp-partner.google.com <gu...@xiaomi.corp-partner.google.com> #4
Dear Google,
Is there any updates about this issue?
Thank you.
Is there any updates about this issue?
Thank you.
vi...@google.com <vi...@google.com> #5
Thanks for reporting this issue.
Could you please confirm if you are still able to reproduce this issue on the latest CTS build, using the most recent device build? Ideally, this should be tested on BP2A
if you have access, or otherwise on BP1A
.
vi...@google.com <vi...@google.com> #6
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
vi...@google.com <vi...@google.com> #7
We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.
Description
This form is only for reporting bugs found in the Android system while
developing Android applications -- please remember to fill out all of your application information in the required fields.
Use the Tools templates for issues with the developer tools.
Please describe the problem in detail. Be sure to include:
- Fill out the required fields.
- Steps to reproduce the problem (including sample code if appropriate).
- What happened.
- What you think the correct behavior should be.
Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).
Please also run "adb bugreport" and archive the output.
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes