Jon Siwek 430f9a92c6 GH-443: fix uses of timestamp 0 in cluster diagnostic logs ... For broker.log and cluster.log: there was a race condition. A worker's first IOSource that it processes is potentially Broker if there were no packets available yet and thread scheduling happens to work out such that network connections (inside CAF threads) become established before we enter the main I/O loop. Such peering establishments would generate logs with timestamp 0 as there was not yet any code path taken that would update network_time. For reporter.log: any non-worker (packet-processing) node would just unnecessarily use a timestamp of 0 for their reporter messages.		2019-06-27 23:00:42 -07:00
..
logger-test.log	GH-443: fix uses of timestamp 0 in cluster diagnostic logs	2019-06-27 23:00:42 -07:00
output	Use .zeek file suffix in unit tests	2019-04-16 16:08:57 -07:00