Skip to content

Conversation

@aaltay
Copy link
Member

@aaltay aaltay commented Nov 6, 2019

This test is flaky when it is run under load. Increasing overhead budget as a temporary fix.

A better solution would be to change the test structure to not depend on specific timings.


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

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • 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.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- Build Status --- --- Build Status
Java Build Status Build Status Build Status Build Status
Build Status
Build Status
Build Status Build Status Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
--- Build Status
Build Status
Build Status
Build Status
--- --- Build Status
XLang --- --- --- Build Status --- --- ---

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website
Non-portable Build Status Build Status
Build Status
Build Status Build Status
Portable --- Build Status --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

This test is flaky when it is run under load. Increasing overhead budget as a temporary fix.

A better solution would be to change the test structure to not depend on specific timings.
@aaltay aaltay requested a review from tvalentyn November 6, 2019 19:12
@tvalentyn
Copy link
Contributor

LGTM. If the test is inherently flaky, we can also add a tenacity retry decorator.

@aaltay
Copy link
Member Author

aaltay commented Nov 6, 2019

LGTM. If the test is inherently flaky, we can also add a tenacity retry decorator.

Done. Good idea, thank you.

overhead_us = 1000000.0 * elapsed_time / state_transition_count

# TODO: This test is flaky when it is run under load. A better solution
# would be to change the test structure to not depend on specific timings.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please copy or move this comment to line 98.

@aaltay
Copy link
Member Author

aaltay commented Nov 7, 2019

Run Portable_Python PreCommit

@aaltay
Copy link
Member Author

aaltay commented Nov 7, 2019

Run Python PreCommit

@aaltay aaltay merged commit 90d5878 into master Nov 8, 2019
@aaltay aaltay deleted the aaltay-patch-1 branch November 8, 2019 00:10
aaltay added a commit that referenced this pull request Nov 26, 2019
Fixes the mistake from #10012. #10012 doubled the measured time instead of the allowed overhead.
aaltay added a commit that referenced this pull request Nov 26, 2019
Fixes the mistake from #10012. #10012 doubled the measured time instead of the allowed overhead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants