-
Notifications
You must be signed in to change notification settings - Fork 52
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
Runtime tests have issues finding the testing app on Android x64 #672
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Failed again in runtime 20210608.73 with One of Error message:
|
@fanyang-mono : another intermittent failure on Android "Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.Open" lane |
Both of the log looks like issues related to the xharness test API. The first one stuck at uninstalling Android app. The second one showed that it couldn't find the Android emulator. @premun @greenEkatherine Could your team take a look at these failures? |
I'm on it @fanyang-mono |
Failed again in runtime 20210629.108 with Failed tests:
One of Error messages:
|
I'm not sure if this is the same failure. build: https://dev.azure.com/dnceng/public/_build/results?buildId=1213972&view=logs&jobId=bb94f37e-a09b-5b51-09b2-ab78e7aa5103&j=bb94f37e-a09b-5b51-09b2-ab78e7aa5103&t=506cadc9-3cc4-5d96-6847-011f75a33382 The console log has only this line: |
@radical This issue tracks Android specific issues. The one you are seeing on windows should be tracked by a different issue. |
Failed again in runtime 20210706.106
One of error messages
|
@greenEkatherine @premun - should this be moved to the dotnet\xharness repo for tracking ? |
@SamMonoRT nice idea, I'm going to transfer it there |
Quick glance it seems like the installation of the app failed because there was no space on the device so probably the runtime tests should fail there and not try further? @fanyang-mono? JIT_jit64_install.output.txt
@greenEkatherine we're tracking this somewhere already, right? |
@premun yes, for issues with 78 exit code and message with "not enough space" either internal or external we raised the issue #660 But also I see there are few logs with 85 exit codes which means we cannot find a device. I need to check it separately |
@greenEkatherine my point was that it seems like the runtime tests call the So I think the exit code can be misleading? And we should probably stop the execution if we fail the installation? |
ah, got it, nice catch! @premun you are right, tests failed with exit code == 85 because installation on previous step failed and we cannot find a device with app installed It means that fix for #660 should solve the issue from our side. @fanyang-mono could you please add a check for an exit code from |
Yes, I will add that check. |
Check was added and related issue was resolved, closing |
Run: runtime 20210526.87
Failed tests:
One of Error messages:
The text was updated successfully, but these errors were encountered: