[ECO-2390] Fix flaky sdk e2e test due to period boundary cross miscalculation #338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CRBl69
approved these changes
Nov 12, 2024
alnoki
approved these changes
Nov 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The
submit.test.tse2e test for the SDK would sometimes fail because it wasn't properly calculating the number of period boundaries crossed between two bump events.To fix it, I added a function that calculates the number of period boundaries crossed between a start time and end time and calculate the number of period boundaries crossed between any two bump event start/end times.
Testing
calculatePeriodicBoundariesCrossedfunctionThe tests will run in CI for this PR.
Checklist