Fix travis failure

[chadwhitacre]

In the grand tradition of #4129 and #4290 ...

[chadwhitacre]

https://travis-ci.org/gratipay/gratipay.com/builds/196760317

[chadwhitacre]

@JessaWitzel Ready for review! :)

re: slack

[chadwhitacre]

For posterity:

It’s not your fault, it’s a spurious test failure.
I tried fixing it once recently but I guess it wasn’t enough.
The ttw tests (the ones that actually load a browser and click around) are sensitive to subtle timing changes.
Like, how long does it take to load the response after clicking a certain button?
Writing those tests is a balancing act between loooong tests (wait ten seconds after clicking the button), and testing too quickly (wait 10 milliseconds after clicking the button).
And we haven’t found the balance point yet on the particular test that’s failing. 🙂

[nobodxbodon]

Wow this sounds flaky. I guess there's no easy way to create some 'wait' method to listen for element change, and then verify if time elapsed isn't too long?

[chadwhitacre]

I think that's a good idea, but can we just do this for now? 🙈

[chadwhitacre]

Bump (and rebased, was 1157e0d).

[mattbk]

I'm happy with this.

[chadwhitacre]

@mattbk I think you could merge?

[chadwhitacre]

💃