scenarios: Unify logs in verify script #64
No reviewers
TrueCloudLab/storage-core-developers
TrueCloudLab/storage-services-committers
Labels
No labels
P0
P1
P2
P3
good first issue
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#64
Loading…
Reference in a new issue
No description provided.
Delete branch "fyrchik/xk6-frostfs:verify-logs"
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?
Close #63.
Close #62.
Close #27.
Close #66.
[#63] scenarios: Unify logs in verify scriptto scenarios: Unify logs in verify script954f0e7e9a
toece55e7f49
ece55e7f49
to7d02136502
@ -85,3 +86,4 @@
if objBytes == nil {
return errors.New("object doesn't exist")
}
if err := oldB.Delete(key); err != nil {
What this do and for?
I suppose it removes object from old bucket, because the object now should belong to the bucket of new status...
Exactly, object must be stored in exactly one bucket, according to its status.
@ -113,1 +118,4 @@
let result;
// Different name is required.
// ReferenceError: Cannot access a variable before initialization.
let lg = log;
Optional: I would name the variable as
objLog
, because we extend the "common" log with object-specific attributes. And comment above probably won't be needed)da95c829c5
tobcb70653df
bcb70653df
to925fe3ec83