-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
test(core): don't fetch full DebugLinkState
by default
#4568
Conversation
|
2140bbe
to
116377b
Compare
no, let's not do that again :( having to propagate on a separate note, this breaks the "read text representation of screens" feature. but i don't think anyone is actually using it? another option is to always return the layout, but make the |
Sounds good, I'll change the code to separate sending
IIUC, the text representation is collected into pytest -vvv ../tests/device_tests/binance/test_get_address.py --record-text-layout
Not sure if there is any other tool that depends on it... |
933fffe
to
1c18a26
Compare
Manually tested on TS5: #4401 (comment) |
1596c8c
to
abb1d59
Compare
DebugLinkState
by default
26ab041
to
a9177c6
Compare
In case the main workflow is restarting after a `DebugLinkDecision`, sending the response of `DebugLinkGetState` may get interrupted. We are making the state fetching explicit, in order to avoid the "restart" race condition (as described in #4401). Following the above change, text-based layout recording is removed. [no changelog]
a9177c6
to
693283f
Compare
Thanks! I have squashed, rebased and updated commit description. |
In case the main workflow is restarting after a
DebugLinkDecision
, sending the response ofDebugLinkGetState
may get interrupted (see #4401).Let's make the full
DebugLinkGetState
fetching explicit, to avoid the "restart" race condition.