You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apparently they are building rocksdb from c++ scratch every darn time, inside the docker container.
I don't thinks RocksDB is changing that much. The docker container could just come with pre-built rocksdb and pre-built c-rockdsb, and this would save a ton of time (and perhaps CI cost).
The text was updated successfully, but these errors were encountered:
make acceptance does cache all the build artifacts (in the host machine
GOPATH; that's what we suspected screwed up your linker) and it does not
usually build RocksDB new at all. Are you sure they do that? We've also had
an issue in which a go list ./... inside of the container takes forever.
On Fri, Jul 8, 2016 at 12:53 PM Jason E. Aten, Ph.D. < [email protected]> wrote:
apparently they are building rocksdb from c++ scratch every darn time,
inside the docker container.
I don't thinks RocksDB is changing that much. The docker container could
just come with pre-built rocksdb and pre-built c-rockdsb, and this would
save a ton of time (and perhaps CI cost).
apparently they are building rocksdb from c++ scratch every darn time, inside the docker container.
I don't thinks RocksDB is changing that much. The docker container could just come with pre-built rocksdb and pre-built c-rockdsb, and this would save a ton of time (and perhaps CI cost).
The text was updated successfully, but these errors were encountered: