Evgenii Stratonikov
d14d065fdc
All checks were successful
Vulncheck / Vulncheck (pull_request) Successful in 2m51s
DCO action / DCO (pull_request) Successful in 2m37s
Build / Build Components (1.21) (pull_request) Successful in 4m9s
Build / Build Components (1.20) (pull_request) Successful in 4m16s
Tests and linters / Staticcheck (pull_request) Successful in 6m6s
Tests and linters / Lint (pull_request) Successful in 6m55s
Tests and linters / Tests (1.20) (pull_request) Successful in 6m57s
Tests and linters / Tests (1.21) (pull_request) Successful in 7m7s
Tests and linters / Tests with -race (pull_request) Successful in 7m3s
Unless tested, generic version can start gaining bugs. With a separate build tag we can have the best of both worlds: 1. Use optimized implementation for linux by default. 2. Run tests or benchmarks for both. Note that they are not actually run automatically now, but this is at leas possible. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com> |
||
|---|---|---|
| .. | ||
| blobovniczatree | ||
| common | ||
| compression | ||
| fstree | ||
| internal/blobstortest | ||
| memstore | ||
| teststore | ||
| blobstor.go | ||
| blobstor_test.go | ||
| control.go | ||
| delete.go | ||
| exists.go | ||
| exists_test.go | ||
| generic_test.go | ||
| get.go | ||
| get_range.go | ||
| info.go | ||
| iterate.go | ||
| iterate_test.go | ||
| logger.go | ||
| metrics.go | ||
| mode.go | ||
| perf_test.go | ||
| put.go | ||
| rebuild.go | ||