-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix integration test that is unstable due to incorrect materialization boundaries #2095
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2095 +/- ##
==========================================
+ Coverage 83.53% 83.71% +0.17%
==========================================
Files 100 100
Lines 8079 8263 +184
==========================================
+ Hits 6749 6917 +168
- Misses 1330 1346 +16
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: pyalex <[email protected]>
Signed-off-by: pyalex <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, pyalex The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: pyalex [email protected]
What this PR does / why we need it:
test_universal_e2e::test_e2e_consistency is flaky since test records' timestamps and materialization boundaries (start and end times) are generated independently. So materialization is inconsistent, most of the time it writes 3 rows, but in some moments it could materialize the whole test dataframe (5 rows) in one go, which is not expected behavior.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: