cmd/snap: improved robustness of unit tests TestWaitWhileInhibitedGraphicalSession* #12535
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.
Problem:
When running
run-checks --unit
with snapsnapd-desktop-integration installed
indevmode
, the unit testsTestWaitWhileInhibitedGraphicalSessionFlow
,TestWaitWhileInhibitedGraphicalSessionFlowError
,TestWaitWhileInhibitedGraphicalSessionFlowErrorOnFinish
fails and or timeout.The underlying issue in all three test is that the target function
graphicalSessionFlow
does not get called due to the presence of DBus andsnapd-desktop-integration
affecting the return values from functiontryNotifyRefreshViaSnapDesktopIntegrationFlow
in an unexpected way. Also, when inhibit state is not unlocked with a mock,tryNotifyRefreshViaSnapDesktopIntegrationFlow
is stuck inwaitInhibitUnlock
loop until timeout (the case with testTestWaitWhileInhibitedGraphicalSessionFlowError
).Solution:
Enabled mocking of
tryNotifyRefreshViaSnapDesktopIntegrationFlow
to predictably exercisegraphicalSessionFlow
as intended.