Fix GC race conditions in tests #668
No reviewers
TrueCloudLab/storage-core-developers
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 milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#668
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fyrchik/frostfs-node:fix-gc-test"
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?
Seems a bit ugly, but I am tired of getting races because of artificial timeouts.
As a benefit we get explicit GC requirements reflected in tests.
a90001a59d
toa48d47d578
a48d47d578
toc65c6a5d03
Fix GC race conditions in teststo WIP: Fix GC race conditions in testsc65c6a5d03
to5ff0443039
5ff0443039
tofca9498c80
fca9498c80
to608c005595
608c005595
toc4f69ced6a
c4f69ced6a
to9754d9c4cc
9754d9c4cc
to4204c3d64b
4204c3d64b
to99734c0948
WIP: Fix GC race conditions in teststo Fix GC race conditions in testsFix GC race conditions in teststo Fix GC race conditions in tests65bc93ea01
tod3ede98cd9