Add "bad" testcases for policer #656
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#656
Loading…
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?
Container is not found, but so is it's deletion info.
Missing from #640
The issue appeared from the discussion.
Unit tests for the policer lack a unit-test where the such scenario is checked:
WasRemoved = false
)So, we need something like this test but with this setup
If you look at the control paths
then you can see that here is a problem how to notify the unit-test that nothing got to bury channel. So, some idea can be used to write the unit-test.
Simple way - add
and itercept this message in the unit-test
7e7dd4dcd9/src/net/tcpsock_posix.go (L58)