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

Device 9CBAY1NP1W is offline #2283

Open
3 tasks
matouskozak opened this issue Mar 18, 2024 · 1 comment
Open
3 tasks

Device 9CBAY1NP1W is offline #2283

matouskozak opened this issue Mar 18, 2024 · 1 comment

Comments

@matouskozak
Copy link
Member

matouskozak commented Mar 18, 2024

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=606476

Build leg reported

net8.0-linux-Release-arm64-Mono_Release_LinuxBionic-Windows.11.Amd64.Android.Open

Pull Request

dotnet/runtime#99449

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "fail: Failed to get device's property SupportedArchitectures. Check if a device is attached / emulator is started",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

It appears that the device 9CBAY1NP1W is offline causing the CI to fail.
Extended error message:

[07:06:56] dbug: Executing command: 'D:\h\w\A87F0953\p\microsoft.dotnet.xharness.cli\8.0.0-prerelease.24112.2\runtimes\any\native\adb\windows\adb.exe -s 9CBAY1NP1W shell getprop ro.product.cpu.abilist'
[07:06:56] warn: Device 9CBAY1NP1W is offline; retrying up to five minutes
[07:06:56] dbug: All 30 retries of action failed
[07:06:56] fail: Failed to get device's property SupportedArchitectures. Check if a device is attached / emulator is started
                 error: device unauthorized.
                 This adb server's $ADB_VENDOR_KEYS is not set
                 Try 'adb kill-server' if that seems wrong.
                 Otherwise check for a confirmation dialog on your device.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=606476
Error message validated: [fail: Failed to get device's property SupportedArchitectures. Check if a device is attached / emulator is started]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/18/2024 5:53:05 PM UTC

Report

Build Definition Test Pull Request
880213 dotnet/runtime System.Xml.Linq.Events.Tests.WorkItemExecution
873764 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
873718 dotnet/runtime System.Runtime.Tests.WorkItemExecution dotnet/runtime#109975
869640 dotnet/runtime System.Net.WebHeaderCollection.Tests.WorkItemExecution
867413 dotnet/runtime System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution
864730 dotnet/runtime System.IO.Pipes.Tests.WorkItemExecution

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 1 6
@akoeplinger
Copy link
Member

akoeplinger commented Jul 23, 2024

@matouskozak I think you need to ping dnceng with the device and host machine names so they can take care of it (if it's a physical device)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants