Skip to content
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

Fixes and improvements of AIO tests #645

Merged
merged 10 commits into from
Dec 10, 2024
Merged

Fixes and improvements of AIO tests #645

merged 10 commits into from
Dec 10, 2024

Conversation

cthulhu-rider
Copy link
Contributor

No description provided.

Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

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

I can't agree with a9aa379, these tests run sequentially, the problem is elsewhere.

pool/pool_aio_test.go Outdated Show resolved Hide resolved
@cthulhu-rider
Copy link
Contributor Author

I can't agree with a9aa379, these tests run sequentially, the problem is elsewhere.

yeah, this should be fixed another way. Tests run independently (and yeah - sequentially), so failed upload object does not prevent download object. The latter uses var that the former sets only in case of success. That's the problem

The fact that 'container really deleted' is already checked in
'container delete' test.

Signed-off-by: Leonard Lyubich <[email protected]>
Returned readers must be closed when no error only, NPE occurs otherwise.

Signed-off-by: Leonard Lyubich <[email protected]>
Previously, some subtests were dependent from each other:
 - eACL must be set after container creation only;
 - eACL must be read after setting (existing test is not about 404 case);
 - any object test must be within container lifetime;
 - object must be downloaded after upload and before removal only;
 - object must be removed after upload only.

Now run order is correct. Independent tests are still run independently
and do not affect each other (e.g. GET and DELETE).

Refs #644.

Signed-off-by: Leonard Lyubich <[email protected]>
There is no 'bucket' term in NeoFS.

Signed-off-by: Leonard Lyubich <[email protected]>
It can be random. The usertest package already provides one.

Signed-off-by: Leonard Lyubich <[email protected]>
The functions are pretty big, declaring vars much earlier they are used
complicates readability.

Signed-off-by: Leonard Lyubich <[email protected]>
They are polling, not 'pooling', and intervals, not timeouts.

Signed-off-by: Leonard Lyubich <[email protected]>
More accepted approach for tests instead of defer.

Signed-off-by: Leonard Lyubich <[email protected]>
Definite misuse of panics.

Signed-off-by: Leonard Lyubich <[email protected]>
@roman-khimov roman-khimov merged commit b312ddb into master Dec 10, 2024
6 of 8 checks passed
@roman-khimov roman-khimov deleted the bugfix/aio-tests branch December 10, 2024 14:01
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