[FW][FIX] fix random errors in tour tests #57145
Closed
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.
Description of the issue/feature this PR addresses:
The simplified version of run method looks like this:
That is, if page is not reloaded, the tour starts immediately. Unfortunately, in rare cases, the method in setTimeout is executed earlier than reloading happens. It brokes the whole tour. For example:
This commit simply increases the timeout in setTimeout to avoid such situations
Current behavior before PR:
Random rare annoying falsy negative results in tour tests in travis
Desired behavior after PR is merged:
Get rid of falsy negative results in CI tests
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
@it-projects-llc
Forward-Port-Of: #40049