Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing Android .apk fails on some machines/devices #45428

Closed
akoeplinger opened this issue Dec 1, 2020 · 7 comments
Closed

Installing Android .apk fails on some machines/devices #45428

akoeplinger opened this issue Dec 1, 2020 · 7 comments
Assignees
Labels
area-Infrastructure-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' untriaged New issue has not been triaged by the area owner

Comments

@akoeplinger
Copy link
Member

E.g. DNCENGWIN-005 and DNCENGWIN-033 in the windows.10.amd64.android.open queue currently hit an issue where installing any .apk hits this error:

Performing Streamed Install
adb: failed to install System.DirectoryServices.Protocols.Tests.apk: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE: Scanning Failed.: Package System.DirectoryServices.Protocols.Tests.apk could not be assigned a valid UID]'
@akoeplinger akoeplinger added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-Infrastructure-mono labels Dec 1, 2020
@ghost
Copy link

ghost commented Dec 1, 2020

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

E.g. DNCENGWIN-005 and DNCENGWIN-033 in the windows.10.amd64.android.open queue currently hit an issue where installing any .apk hits this error:

Performing Streamed Install
adb: failed to install System.DirectoryServices.Protocols.Tests.apk: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE: Scanning Failed.: Package System.DirectoryServices.Protocols.Tests.apk could not be assigned a valid UID]'
Author: akoeplinger
Assignees: -
Labels:

area-Infrastructure-mono, blocking-clean-ci

Milestone: -

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 1, 2020
@akoeplinger akoeplinger self-assigned this Dec 1, 2020
@MattGal
Copy link
Member

MattGal commented Dec 1, 2020

I'm going to try to address this as part of the "surge".

@ericstj
Copy link
Member

ericstj commented Dec 1, 2020

I'm seeing this in a ton of PRs, does immediate action need to be taken?

[10:23:52] dbug: Executing command: 'C:\h\w\AEAA09A9\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.20576.3\runtimes\any\native\adb\windows\adb.exe -s 014AY1RPX0 install "C:\h\w\AEAA09A9\w\A30D08BF\e\Microsoft.Extensions.Configuration.EnvironmentVariables.Tests.apk"'
[10:23:55] fail: Error:
                 Exit code: 1
                 Standard Output:
                 Performing Streamed Install
                 
                 Standard Error:
                 Performing Streamed Install
                 
                 
[10:23:55] crit: Install failure: Test command cannot continue
XHarness exit code: 78

@akoeplinger
Copy link
Member Author

akoeplinger commented Dec 1, 2020

@ericstj if this is a PR that ran in the last ~24hours then it probably ran on DNCENGWIN-005 which hit the issue. We disabled that machine in Helix about an hour ago so it shouldn't be hit anymore right now.

@ericstj
Copy link
Member

ericstj commented Dec 2, 2020

Yeah, I noticed in about 6 different PRs I sampled that ran in the last 16 hours or so. Good to know that this has been mitigated. Thanks @akoeplinger and @MattGal

MattGal added a commit to MattGal/xharness that referenced this issue Dec 2, 2020
…all cache is full or something, rebooting device helps. Also improve wait-for-device to actually check the boot_completed prop
@MattGal
Copy link
Member

MattGal commented Dec 2, 2020

akoeplinger pushed a commit to dotnet/xharness that referenced this issue Dec 2, 2020
…all cache is full or something, rebooting device helps. Also improve wait-for-device to actually check the boot_completed prop (#388)

There seems to be a mystery state where the install cache is full or something, rebooting device helps.  

Also improve wait-for-device to actually check the boot_completed property (exposed by rebooting devices) and fix standard error logging bug pointed out by akoeplinger that's been there forever.
@akoeplinger
Copy link
Member Author

The xharness bump landed with #45476 and I verified the fix is working (dotnet/xharness#354 (comment)).

@ghost ghost locked as resolved and limited conversation to collaborators Jan 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

4 participants