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
Hello there,I recently tried the robotframework-retryfailed library https://docs.robotframework.org/docs/flaky_tests
I wanted to give the flaky tests the ability to start a second run if they fail due to e.g. timeout
My problem is that it basically works perfectly, but not in Docker Here it makes my defined repeat attempt of :1 in an endless loop
Does anyone have experience with this or the same problem? Thx
Here the output from console:
Thx
The text was updated successfully, but these errors were encountered:
i am having the same issue here , did you managed to resolve it ?
Sorry, something went wrong.
Hi Mohamed, I have found a solution or workaround that gets around the problem
It involves a bit of copy pasting.
The tests are no longer carried out by command
robot --listener RetryFailed <your robot suite>
but you add the library and the number of retries in each individual robot file under Settings
Solution:
*** Settings *** Library RetryFailed global_retries=1
Now run the tests normally as before without the above command
Thanks Fabisento i will give it a try
No branches or pull requests
Hello there,I recently tried the robotframework-retryfailed library
https://docs.robotframework.org/docs/flaky_tests
I wanted to give the flaky tests the ability to start a second run if they fail due to e.g. timeout
My problem is that it basically works perfectly, but not in Docker
Here it makes my defined repeat attempt of :1 in an endless loop
Does anyone have experience with this or the same problem? Thx
Here the output from console:
Thx
The text was updated successfully, but these errors were encountered: