hodooor / Hodoor

Server side for Hodoor - Casual attendance system
GNU General Public License v3.0
8 stars 6 forks source link

Travis failing probably because of chromedriver #128

Closed DavidKozina closed 6 years ago

DavidKozina commented 6 years ago
...
 File "/home/travis/virtualenv/python3.5.4/lib/python3.5/site-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.34.522913 (36222509aa6e819815938cbf2709b4849735537c),platform=Linux 4.14.12-041412-generic x86_64)
...

This is going on since Jan 12, 2018 It first failed after this commit: f4979e2b053cb23bb9c65529de5380bb9df93a88 with this log: https://travis-ci.org/hodooor/Hodoor/builds/328114384?utm_source=github_status&utm_medium=notification

I don't see why...

OndrejVicar commented 6 years ago

It's because chromedriver is not compatibile with version of chrome.

DavidKozina commented 6 years ago

So we use:

Do we need newest browser for testing? If so we have to upgrade chromeDriver too and hope that we will not be force to upgrade selenium.

Or we still can use older version of Chrome and specific it in .travis.yml file.

OndrejVicar commented 6 years ago

We should always use the newest version of a browser and choose compatible versions of selenium and driver.

DavidKozina commented 6 years ago

@OndrejVicar, i thought so.

In PR #129 it's always use newest Chrome, newest ChromeDriver and I update Selenium. I prefer use fix version of selenium because of possibly syntax changes of code. All tests have passed

OndrejVicar commented 6 years ago

Solved by #129