9 Commits (3795fd77e7ca3a696f63f6fa14bd8e6f57c5c5b0)

Author	SHA1	Message	Date
Nelson Elhage	2080122f38	WaitForLeader: Also wait for a non-zero index. ... On my laptop, I'm currently seeing a huge number of intermittent test failures all related to WaitForLeader returning after the test node has become a leader, but before it has actually finished starting up, in particular, performing the serf/Raft reconciliation. Waiting for the index to become nonzero makes the tests pass reliably, by also blocking until the new leader has started committing state.	2014-05-26 13:26:42 -07:00
Armon Dadgar	14be60aaca	gofmt	2014-05-20 16:25:29 -07:00
William Tisäter	76d9fa255b	Speed up test runs in `WaitForResult`	2014-05-09 03:00:43 +02:00
William Tisäter	e1d111a43d	Increase timeout for `WaitForResult`	2014-05-09 02:43:48 +02:00
William Tisäter	78145ecfd5	Require datacenter argument for `WaitForLeader`	2014-05-09 01:17:35 +02:00
William Tisäter	c8168bd8fe	Drop client arguments from `WaitForLeader`	2014-05-07 23:41:14 +02:00
William Tisäter	aa00bfff7d	Fix `TestCatalogListNodes_StaleRaad` with `WaitForLeader`	2014-05-07 13:53:29 +02:00
William Tisäter	f1b9dbe5c3	Add `testutils.WaitForLeader` and truly wait	2014-05-07 11:43:42 +02:00
William Tisäter	028bc7e1b4	Proof of concept using `WaitForResult` in tests	2014-05-07 02:48:25 +02:00