Closed (fixed)
Project:
Panopoly
Version:
7.x-1.x-dev
Component:
Tests / Continuous Integration
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Jul 2015 at 16:40 UTC
Updated:
25 Aug 2015 at 13:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dsnopekComment #2
dsnopekThe last successful build was using Chrome 43, and then subsequent failed build was on Chrome 44. I suspect that's the cause of these failures!
Locally, I'm still using Chrome 43, so I'll try upgrading. But it could also be an incompatibility with the chrome-sandbox binary that we're downloading, so it could be a Travis only failure too...
Comment #3
dsnopekI get the same failures locally when using Chrome 44! I tried updating my local copy of 'chromedriver' (not knowing what version it was) to 2.16 and that didn't help. I'm already using Selenium 2.46 which is the latest version. I've been Googling to find anyone else reporting this problem, but I haven't found anything yet...
Comment #4
dsnopekHere's a patch that will pin the tests to Chrome 43, which has been working in my testing!
I've also simultaneously been attempting to get to the root of the problem, because I really like to be able to use the latest Chrome. So, I did a bit of investigating and posted an issue to the MinkSelenium2Driver project:
https://github.com/minkphp/MinkSelenium2Driver/issues/213
I'll try to keep following up with them and ultimately get an issue created in the correct issue queue!
But if that takes too long, we have this patch. :-)
Comment #6
dsnopekI feel like I'm getting closer to the underlying problem, but for now, I'm just going to commit this so we can get back to making Panopoly awesome. :-)
Here's the Travis-CI build: https://travis-ci.org/panopoly/panopoly/builds/72484620
Comment #7
dsnopekFYI, work on the underlying Chrome issue has moved to this issue:
https://code.google.com/p/chromium/issues/detail?id=513768
It sounds like the Chrome developers are close to a solution!
Comment #8
dsnopekSupposedly, this is fixed now:
https://code.google.com/p/chromium/issues/detail?id=513768
We should be able to roll this back! However, I'd like to keep the mechanics for it around in case we have to do this again (at least until we switch to drupal_ti):
#2545580: Use latest Chrome on Travis-CI