mirror of
https://github.com/nspcc-dev/neofs-testcases.git
synced 2026-03-01 04:29:19 +00:00
Flaky test_rest_headers suite #395
Labels
No labels
I1
I2
I3
I4
S0
S1
S1
S2
S3
S4
U0
U0
U1
U2
U3
U4
blocked
bug
dependencies
discussion
documentation
enhancement
enhancement
enhancement
epic
feature
good first issue
help wanted
performance
question
task
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-testcases#395
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cthulhu-rider on GitHub (Jun 23, 2025).
Current Behavior
fail occured once
Expected Behavior
either always pass or fail
Possible Solution
perhaps the problem is on NeoFS side. Need to explore
i also noticed that in failure case same OID occured in different suites. In such cases, a read-delete race is usually suspected
Context
https://github.com/nspcc-dev/neofs-node/pull/3406
Regression
maybe
@cthulhu-rider commented on GitHub (Jun 23, 2025):
not reproduced locally after 5 attempts
@evgeniiz321 commented on GitHub (Jul 3, 2025):
@roman-khimov seems like a bug in rest gw for me, there are 2 objects with same attribute -
'Writer': 'Leo Tolstoy'. Test removes one, then tries to get a second object by this attribute but gets an errorstatus: code = 2052 message = object already removed. get by id works ok. Not sure why it reproduced once, maybe some caching issue?@roman-khimov commented on GitHub (Jul 4, 2025):
It looks like cache or search returning an old ID which is then unavailable. Depending on specifics it's either a feature or a bug. @evgeniiz321, can you look into logs to check what really happens there?
@evgeniiz321 commented on GitHub (Aug 4, 2025):
waiting for a reproduction