featurebase/test
Seebs 1e0873c70b lock BufferLogger for reads/writes
With the new addition of the holder background scan, it's possible
for an open holder to write log messages at arbitrary times. The
TestHolder_Open/ErrIndexName test checks the contents of the output
buffer, but those contents could be changing if the background task
happens to run at the right time. Use trivial locking around that
so that this shouldn't happen.
2019-11-12 12:15:13 -06:00
..
cluster.go remove the last usages of test.NewExecutor and cleanup unused in test package 2018-07-01 07:31:31 -05:00
field.go v2.0.0 2019-10-08 14:56:17 -06:00
handler.go remove the last usages of test.NewExecutor and cleanup unused in test package 2018-07-01 07:31:31 -05:00
holder.go v2.0.0 2019-10-08 14:56:17 -06:00
index.go v2.0.0 2019-10-08 14:56:17 -06:00
logger.go lock BufferLogger for reads/writes 2019-11-12 12:15:13 -06:00
pilosa.go initial gRPC server implementation 2019-10-29 14:27:07 -05:00
pilosa_test.go v2.0.0 2019-10-08 14:56:17 -06:00