Device registration e2e test sometimes times out while checking that the device was registered
- Dominant language
- Go
- Stars
- 308
- Forks
- 41
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 58
Description
I've seen `Test device registration during device code flow` fail with
```
TimeoutExpired: Command '['/home/runner/work/authd/authd/e2e-tests/resources/ssh.sh', '--', "sudo find -L /var/snap/authd-msentraid/current -path '*/e2e-test@ubudev1.onmicrosoft.com/token.json'"]' timed out after 30 seconds
```
in step `Check That Device Was Registered`.
Observed in https://authd-e2e-test-logs.adrian-dombeck.workers.dev/push-33891271000/run-33891271000-1/resolute-authd-msentraid/log.html#s1-s11
Contributor guide
Research direction
Start with the `Test device registration during device code flow` e2e test and its `Check That Device Was Registered` step, then inspect `e2e-tests/resources/ssh.sh` and the linked run logs. Determine why the remote `find` command exceeds 30 seconds and make the check reliably complete while still confirming `token.json` exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100