-
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: Unable to find visible select box "residence_document_type" that is not disabled #1209
Comments
I'll do this one |
This seems to be a time zone related issue, it is still happening in a build ran at ~01:00 |
I check the time zone issue and do the backport |
@raul-fuentes I'm very sorry I hadn't noticed this issue was already open! These flaky specs should be fixed by consul#2712, which was originally opened to fix consul#2520 and consul#2521. |
All these failures have happened again on a build run at ~01:00 A.M.: https://travis-ci.org/javierm/consul/jobs/422313695 However, they now a different error message:
|
Closed via consul#2712 and #1625. |
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: 63774
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: