-
Notifications
You must be signed in to change notification settings - Fork 249
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
intermittent failures #1803
Comments
here are the cucumber profiles on LocalSupport that make the rerun of failures possible: https://github.com/AgileVentures/LocalSupport/blob/develop/config/cucumber.yml the trick for WSO would be to make this all work for semaphore, but that shouldn't be a big deal ... hahahahahha |
ah, so I'm the odd one out for that vote on test re-run happy to concede to the majority just noting we've never done it on semaphore before and it requires admin input |
restarting builds is burning time - must sort this ... |
are a real pain in CI - I wonder if we should replicate what @johnnymo87 set up for us on LocalSupport which is re-running any failed tests a second time to see if they are "real" failures ...
I note a few open issues covering specific intermittent fails:
#1084 #1078 #997 #995 #994
doing a re-run on individual failures seems a better practice than the omission strategy that we currently use, and the re-run should also mean it's easier to find the error messages in the semaphore logs ...
The text was updated successfully, but these errors were encountered: