store/postgres: Get rid of the Travis logging hack again
It may not be necessary anymore (who knows why).
use fallible_iterator::FallibleIterator;
use postgres::{Connection, TlsMode};
-use std::env;
-use std::io;
use std::sync::atomic::{AtomicBool, Ordering};
use std::sync::{Arc, Barrier};
use std::thread;
@@ -91,20 +89,6 @@ impl EntityChangeListener {
return;
}
- // HACK: Travis seems to have serious problems with running the
- // integration tests for the Diesel store. Unless we log frequently
- // from this thread, it all store tests either take a long time
- // or never finish (before Travis' 10mins timeout).
- // As soon as you log something from this thread, suddenly all
- // tests run relatively fast and reliable. This _could_ be a
- // timing-sensitive synchronization issue on our side we've tried
- // almost everything and this hack was the only thing that made
- // the tests work in Travis.
- if env::var("TRAVIS").is_ok() {
- print!(".");
- io::stdout().flush().unwrap();
- }
-
match notification {
Ok(notification) => {
// Parse payload into an entity change
