Infeasible
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please share the test log and full bug report.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Please share the test log and full bug report.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
vi...@google.com <vi...@google.com> #3
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> #4
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
Tool version : CTS 15_r2
AOSP version : android-15.0.0_r1
Issues : CtsBackupTestCases fail
According to the comment of the commit below, it mentions that the test is only possible with the system user, and it is expected to fail on multi-user and automotive devices.
+ <!-- Run module in system user because backup tests are not fully supported in secondary user.
+ For devices running on secondary user, such as automotive devices, these tests will fail.
+ When backup tests are fully functional for secondary users:
+ -change not_secondary_user to secondary_user.
+ -remove SwitchUserTargetPreparer
+ -->
Indeed, the test passed on the system user, not multi-user.
We conduct CTS full tests on multi-user and automotive devices and report the results on the Google Partner site. Since it's a multi-user setup, this test fails. Can we process a waiver for this item? Please let me know how to proceed.
I'll wait for your response.
Thanks.