Upgrade the version of chromedriver in travis to 2.36.
This seems to solve the current build failure on master and on #314 but there are now selenium timeout errors on some runs. I tried to increase the page load timeout without much success.
I ran the system tests job for 7c83605 ten times and I got five pass and five fails. On the other hand I didn't get a single travis timeout. I'm starting to think that this error is a different manifestation of the same thing that made the test suite hang and travis kill the job before. I don't know how to test this hypothesis though, if someone has an idea? (I did look into the release notes for chromedriver but didn't notice anything relevant).
Upgrade the version of chromedriver in travis to 2.36. This seems to solve the current build failure on master and on #314 but there are now selenium timeout errors on some runs. I tried to increase the page load timeout without much success.
I ran the system tests job for 7c83605 ten times and I got five pass and five fails. On the other hand I didn't get a single travis timeout. I'm starting to think that this error is a different manifestation of the same thing that made the test suite hang and travis kill the job before. I don't know how to test this hypothesis though, if someone has an idea? (I did look into the release notes for chromedriver but didn't notice anything relevant).