Skip to content
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

Use the waitForEvent helper function in the text layer integration tests #18555

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

timvandermeij
Copy link
Contributor

The waitForClick helper function is functionality-wise mostly a reduced copy of the more generic waitForEvent helper function that we use for other integration tests, so we can safely replace it to reduce the amount of code.

Moreover, the waitForClick code is prone to intermittent failures given recent assertion failures we have seen on the bots (one of them is linked in #18396) while waitForEvent has recently been fixed to avoid intermittent failures, so usiong it should also get rid of the flakiness for these integration tests.

Fixes a part of #18396.

…tests

The `waitForClick` helper function is functionality-wise mostly a
reduced copy of the more generic `waitForEvent` helper function that
we use for other integration tests, so we can safely replace it to
reduce the amount of code.

Moreover, the `waitForClick` code is prone to intermittent failures
given recent assertion failures we have seen on the bots (one of them
is linked in mozilla#18396) while `waitForEvent` has recently been fixed to
avoid intermittent failures, so usiong it should also get rid of the
flakiness for these integration tests.
@timvandermeij
Copy link
Contributor Author

/botio integrationtest

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Received

Command cmd_integrationtest from @timvandermeij received. Current queue size: 0

Live output at: http://54.241.84.105:8877/7eb280a10c83d87/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Received

Command cmd_integrationtest from @timvandermeij received. Current queue size: 1

Live output at: http://54.193.163.58:8877/f44a0df18d03a54/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Success

Full output at http://54.241.84.105:8877/7eb280a10c83d87/output.txt

Total script time: 8.70 mins

  • Integration Tests: Passed

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Success

Full output at http://54.193.163.58:8877/f44a0df18d03a54/output.txt

Total script time: 18.18 mins

  • Integration Tests: Passed

Copy link
Contributor

@nicolo-ribaudo nicolo-ribaudo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for cleaning this up, and sorry for having introduced the flake! The reason I originally introduced a new helper was that I didn't realize I could use the "validator" to call e.preventDefault().

Copy link
Contributor

@calixteman calixteman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you.

@timvandermeij
Copy link
Contributor Author

@nicolo-ribaudo No worries; I also didn't catch this during review, and such intermittent issues unfortunately often only tend to show up after a number of runs, and on the slower bot which makes it hard to reproduce locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants