Repository navigation
test: wait longer for account discovery in login test and dump logcat on CI failure - #254
Merged
Merged
Conversation
wernrab
approved these changes
Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
LoginTest.loginAndRemoveAccountfailed twice in a row on #234 (pipelines 210 and 211). Pipeline 212 then passed on the same commit without any code changes. Both failures had the same cause. The sign-in worked, but the app stayed on "Preparing account for first launch" (account discovery againstcloud.rc.opencloud.rocks) for longer than the 20 s Kaspresso timeout, so the avatar button never appeared.LoginTest: the check for the main screen's avatar button now waits up to 60 s viaflakySafely(timeoutMs = 60_000L). All other steps keep the 20 s default..woodpecker/integration-test.yml: when the integration test step fails, the EXIT trap now also prints the full device logcat. CI currently only keeps theRetryRulemessages, so the reason for a hang can't be seen.retries.logis written exactly as before, so the test results step works unchanged.