The test-treemanifest-pushrebase test was failing in our continuous integration
environment with a perplexing error:
$ pushclients + abort: exporting bookmark master failed!
(plus some additional failures later)
I thought this should not be possible because of the redirect, but it turns out
that the order of the redirects matters:
>/dev/null 2>&1 redirects both stderr and stdout to /dev/null, but
2>&1 >/dev/null redirects stdout to /dev/null and stderr to stdout
However, this was the only clue to the issue that was going on, and so it's
better to actually keep the error around, if one occurs, so I removed the 2>&1
Furthermore, the test was failing with various clients failing to push.
To increase the chance of this succeeding, I'm bumping the sleep time. Ideally,
we should wait for the server to be "ready", but I'm not certain what that means
or how to test and would like to discuss to figure it out. This hopefully will
unblock the continuous integration for now.