Closed vvarg229 closed 1 year ago
If it's really a bug, then the tests https://github.com/nspcc-dev/neofs-testcases/issues/535 was falling correctly.
@vvarg229 IIUC we set exp
to epoch N
(99), and send request at epoch N
. Currently, resulting behavior is expected and corresponds to the implementation: request is valid at epoch N
and invalid starting from N+1
we have an open issue in protocol related to this topic https://github.com/nspcc-dev/neofs-api/issues/253
if I didn't mess up the epoch numbers, i suggest to rework the test:
exp
exp+1
No bug.
The tests "Validate static session which expires at next epoch" and "Validate static session that is valid" do not work because the session token has not expired.
If I understand correctly, after the second tick of the epoch:
self.tick_epoch()
we expect to get an error "session token has expired", but it's not happening:
See logs: https://github.com/nspcc-dev/neofs-node/actions/runs/5267489783/jobs/9522807183 https://nspcc-dev.github.io/neofs-node/208/#categories/4b1b218519a23f484ef3888ffcf04b79/bcbea02514c8dda1/
Expected Behavior
We should get a message that the session token has expired.
Current Behavior
Steps to Reproduce (for bugs)
Run automated system tests.
Context
I'm trying to get consistently green tests.
Regression
Yes
Your Environment