Fix flaky spec for mobile version of the search form#11558
Merged
andreslucena merged 1 commit intodevelopfrom Sep 12, 2023
Merged
Fix flaky spec for mobile version of the search form#11558andreslucena merged 1 commit intodevelopfrom
andreslucena merged 1 commit intodevelopfrom
Conversation
alecslupu
approved these changes
Sep 8, 2023
Contributor
There was a problem hiding this comment.
LGTM.
By looking at the changed code, i can see that we reduce the animation from 500 to 50 ms.
I have tried to replicate (make it fail with the advertised error on develop) it on my local, but i was not able.
@andreslucena please feel free to merge it.
Member
Author
At least with the parallel_spec approach I could reproduce it pretty fast (in less than 2 minutes). I'll try to clean-up this approach in the next flaky that I find. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎩 What? Why?
This past week I saw a couple of times a flaky spec related to the mobile search.
See example in CI. As this will expire in a couple days, here's the relevant output:
And this is what the screenshot is giving us:
Seeing the relevant lines of the spec itself:
decidim/decidim-core/spec/system/search_spec.rb
Lines 39 to 40 in 8449f41
My hypothesis on what's happening is the following:
Testing
As this is a flaky, it's difficult to test. I found two strategies for now. In both strategies you should check the failure first in
developand then you should apply this PR and run it again to see that it doesn't fail anymore.Slow strategy
In a bash shell:
Fast strategy
I'm still working on refining a bit this one, but it's using the same sequential approach with also a parallel one 🚀.
Steps to follow:
What I could not find the way (for now) is to stop in a failing spec, so you need to check out the output to see if there's a FAILED spec manually 😞