We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TestCustomToolWithSSHGitCreds seems to be flakey as shown in logs here and here and mentioned in #9054.
The cause seems to be that the status for the App doesn't reach a status of Synced. This causes the test to be timed out and fail.
#9054 attempted to fix this, but it does not appear that even 30 seconds is enough some times.
We should consider raising the timeout more or figuring out if the test needs further changes.
The test was introduced in #8389.
The text was updated successfully, but these errors were encountered:
@danielhelfand I notice that the command being printed by the flakey test shows --timeout 10. I wonder if a second timeout needs to be extended.
--timeout 10
Sorry, something went wrong.
This test will be removed in #9105 so closing this.
No branches or pull requests
Summary
TestCustomToolWithSSHGitCreds seems to be flakey as shown in logs here and here and mentioned in #9054.
The cause seems to be that the status for the App doesn't reach a status of Synced. This causes the test to be timed out and fail.
#9054 attempted to fix this, but it does not appear that even 30 seconds is enough some times.
We should consider raising the timeout more or figuring out if the test needs further changes.
The test was introduced in #8389.
The text was updated successfully, but these errors were encountered: