This reworks step execution so that as each step finishes, the other pending steps are tried. It relies on Vert.X to honor its threading policy and keep all the event handling in one thread. (So we can assume that, while we're checking things, states (which are set in the event thread) don't change.)
Achtung! I had to increase the timeout to 1.5 sec on the incomplete pipeline test to get it to complete when I ran it from mvn on the command line on my box. For this circumstance, I don't care how long it takes to resolve, but when it's a search that has executed 5 of its 200 searches, I want to see it right away. I'm not sure at the moment why it would take so long. Further investigation is warranted.
The coverage report prompted me to fix a bug it revealed and write some tests. Of course, I'm seeing some odd behavior, so... working on fixing that now.
This reworks step execution so that as each step finishes, the other pending steps are tried. It relies on Vert.X to honor its threading policy and keep all the event handling in one thread. (So we can assume that, while we're checking things, states (which are set in the event thread) don't change.)
Achtung! I had to increase the timeout to 1.5 sec on the incomplete pipeline test to get it to complete when I ran it from mvn on the command line on my box. For this circumstance, I don't care how long it takes to resolve, but when it's a search that has executed 5 of its 200 searches, I want to see it right away. I'm not sure at the moment why it would take so long. Further investigation is warranted.