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

Try deflaking test timing #32351

Merged
merged 4 commits into from
Aug 28, 2024
Merged

Try deflaking test timing #32351

merged 4 commits into from
Aug 28, 2024

Conversation

damccorm
Copy link
Contributor

As pointed out in #32237 (comment) this test can be flaky. This tests that after 20 is processed (and times out) and at least 10 (2*timeout) seconds have passed, that the model will be full deleted.

Right now, it relies on timing and assumes that the pcollection will be processed in order (or at least the 20 will be processed early). This tries to deflake the test by adding some more elements which are guaranteed to timeout to ensure that after the first times out, sufficient time will pass for garbage collection to occur. It does admittedly lengthen the time to run to ~1 minute, unfortunately.


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@damccorm
Copy link
Contributor Author

R: @Abacn

Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

Copy link
Contributor

@Abacn Abacn 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 the quick fix

feel free to merge after tests pass

@damccorm damccorm merged commit 7d6f6fb into master Aug 28, 2024
102 checks passed
@damccorm damccorm deleted the users/damccorm/ri_test branch August 28, 2024 20:47
@Abacn
Copy link
Contributor

Abacn commented Aug 30, 2024

it's still flaky: https://github.com/apache/beam/actions/runs/10624250387/job/29452206127

as it only happens on windows, we can revert this change and skip this test on windows os instead

damccorm added a commit that referenced this pull request Sep 10, 2024
@damccorm damccorm mentioned this pull request Sep 10, 2024
3 tasks
damccorm added a commit that referenced this pull request Sep 10, 2024
* Revert "Try deflaking test timing (#32351)"

This reverts commit 7d6f6fb.

* Dont run flaky test on windows
reeba212 pushed a commit to reeba212/beam that referenced this pull request Dec 4, 2024
* Try deflaking test timing

* Add another potential timeout

* Simpler technique
reeba212 pushed a commit to reeba212/beam that referenced this pull request Dec 4, 2024
* Revert "Try deflaking test timing (apache#32351)"

This reverts commit 7d6f6fb.

* Dont run flaky test on windows
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.

2 participants