Closed
Description
Test TestWalkBlobs under Content package lasts a little long time, as reporting as,
$ go test -test.run TestWalkBlobs
PASS
ok github.com/containerd/containerd/content 135.422s
To notify that it loops 4M number of writing blobs.
I think it had better to use BeenchMark test, instead usual general go test.
If it should be done, and no one doing yet, I'd like to take it.
Metadata
Metadata
Assignees
Labels
No labels