remote/client: update resources before checking NetworkSerialPort availability #941
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
PR #935 added async waiting for the NetworkSerialPort. This makes
labgrid-client console --loopwork as long as the resource changes from being unavailable to being available. It does not work vice versa, however: the resources are not being updated before being checked for availability. The code inside the while loop does not run in this case.This makes the subsequent
target.await_resources()raise a NoResourceFoundError which is not handled anywhere causing an error message and exit of labgrid-client despite being called with--loop.Fix that by updating the resources before checking the resource's availability.
labgrid-client console --loopwill now loop even if the NetworkSerialPort changes from being available to unavailable.Checklist
Fixes #935
Fixes #926