[#219] Use zaptest.Logger #219
No reviewers
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-http-gw#219
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-http-gw:feature/suppress_log_in_succeded_tests"
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?
Use zaptest to get logs which get printed only if a test fails
or if you ran go test -v.
Dont use zaptest.Logger for fuzz otherwise ngfuzz/libfuzz crashes
Signed-off-by: Denis Kirillov d.kirillov@yadro.com
Similar to TrueCloudLab/frostfs-s3-gw#646
[#XX] Use zaptest.Loggerto [#219] Use zaptest.Logger2d10f852e3
toa651b5823f
@ -93,3 +85,1 @@
}
file, err := fetchMultipartFile(logger, r, bound)
file, err := fetchMultipartFile(zap.NewNop(), r, bound)
I think S3 uses
zaptest.NewLogger()
in TrueCloudLab/frostfs-s3-gw#646Should we use Nop logger?
This is used in bench, then it makes sense.