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

Metabase's SELECT test fail #2917

Closed
carpawell opened this issue Aug 14, 2024 · 0 comments
Closed

Metabase's SELECT test fail #2917

carpawell opened this issue Aug 14, 2024 · 0 comments
Assignees
Labels
bug Something isn't working I4 No visible changes S4 Routine test Unit tests U1 Critically important to resolve quickly

Comments

@carpawell
Copy link
Member

--- FAIL: TestDB_SelectPayloadHash (0.03s)
    db_test.go:41: 
        	Error Trace:	/home/runner/work/neofs-node/neofs-node/pkg/local_object_storage/metabase/db_test.go:41
        	            				/home/runner/work/neofs-node/neofs-node/pkg/local_object_storage/metabase/select_test.go:382
        	Error:      	"[]" should have 1 item(s), but has 0
        	Test:       	TestDB_SelectPayloadHash
FAIL

Expected Behavior

Test works.

Current Behavior

Test does not work.

Possible Solution

Workers are much slower now, it can be related to some parallel background jobs like in the #2860.

Steps to Reproduce (for bugs)

Not sure it is stable.

Context

Firstly saw in #2916.

Regression

Not sure.

@roman-khimov roman-khimov added U2 Seriously planned S4 Routine I4 No visible changes test Unit tests bug Something isn't working U1 Critically important to resolve quickly and removed U2 Seriously planned labels Aug 14, 2024
carpawell added a commit that referenced this issue Aug 20, 2024
SDK somehow generates a random checksum (with a random type too) every time now,
so the old tests should be ready for it (do not use test SDK package in fact).
Closes #2917, and improves test granularity a little.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell added a commit that referenced this issue Aug 20, 2024
SDK somehow generates a random checksum (with a random type too) every time now,
so the old tests should be ready for it (do not use test SDK package in fact).
Closes #2917, and improves test granularity a little.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell added a commit that referenced this issue Aug 20, 2024
SDK somehow generates a random checksum (with a random type too) every time now,
so the old tests should be ready for it (do not use test SDK package in fact).
Closes #2917, and improves test granularity a little.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell added a commit that referenced this issue Aug 21, 2024
SDK somehow generates a random checksum (with a random type too) every time now,
so the old tests should be ready for it (do not use test SDK package in fact).
Closes #2917, and improves test granularity a little.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working I4 No visible changes S4 Routine test Unit tests U1 Critically important to resolve quickly
Projects
None yet
Development

No branches or pull requests

2 participants