-
Notifications
You must be signed in to change notification settings - Fork 18
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
Sync epoch #622
Sync epoch #622
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -202,7 +202,7 @@ def test_session_token_expiration_flags( | |
session=session_token, | ||
) | ||
|
||
self.tick_epochs(2) | ||
self.tick_epochs_and_wait(2) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. iiuc if so, for cases like this, we may lighten requirement to different values matching the condition (e.g. if we tick from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Different tests can have different requirements, so having a single current epoch is safer. And it's feasible in general, the next epoch update is expected to happen long after the current one once it's updated. If we have premature epoch ticks from IR that's a problem and failing a test in this case is appropriate behaviour. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i'd leave the tests granular and, if possible, not adding dependencies on other subsystems (we test them separately). Such a test may fail on a strange tick, but this may not be a node's token verification bug. If epoch is OK, then token is OK, and vice versa, no matter how they tick. Stronger precondition does not improve the test IMO this is my developer vision, may be @vvarg229 @evgeniiz321 have other opinion There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What if you want to test token's There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cthulhu-rider let's continue the discussion in another issue? |
||
|
||
with allure.step("Verify object operations with created session token are not allowed"): | ||
file_path = generate_file(simple_object_size) | ||
|
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.
is it ok that current_epoch won't be really current? shouldn't it be updated inside the cycle?
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.
That's right - we are comparing the current epoch and the epoch that will be after the ticking.