forked from consuldemocracy/consuldemocracy
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Flaky spec: Polls Booth & Website Already voted on booth cannot vote on website #1208
Closed
3 tasks
Labels
Comments
Happened again at https://travis-ci.org/AyuntamientoMadrid/consul/jobs/338257526 |
I think that this flaky is related to this one: #1195 |
I'm doing this. |
This was referenced Jul 1, 2018
Closed by #1342 |
I'll backport this one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Warning!
This spec probably only fails between 00:00 and 02:00 am Madrid time
What
Tests that fail randomly are called "flakies", this one seems to be one:
Randomized seed: 31908
Failure:
How
Tips for flaky hunting
Random values issues
If the problem comes from randomly generated values, running multiple times a single spec could help you reproduce the failure by running at your command line:
You can also try running a single spec in Travis:
Add option
:focus
to the spec and push your branch to Github, for example:But remember to remove that
:focus
changes afterwards when submitting your PR changes!Test order issues
Running specs in the order they failed may discover that the problem is that a previous test sets an state in the test environment that makes our flaky fail/pass. Tests should be independent from the rest.
After executing rspec you can see the seed used, add it as an option to rspec, for example:
bin/rspec --seed 55638
(check Randomized seed value at beginning of issue)Other things to watch for
The text was updated successfully, but these errors were encountered: