Starting a couple days ago, all the Chrome tests are failing on Travis-CI. Here's the output of one such test:

  @api @javascript @chrome @panopoly_wysiwyg @panopoly_wysiwyg_image @panopoly_images @drupal_private_files
  Scenario: Upload an image with format and alt text                                  # features/wysiwyg_media.feature:25
    Given I am logged in as a user with the "administrator" role                      # Drupal\DrupalExtension\Context\DrupalContext::assertAuthenticatedByRole()
      Failed to log in as user 'yc4cFX5S' with role 'administrator' (Exception)

https://travis-ci.org/panopoly/panopoly/jobs/72125794#L2567

I'm not sure what's causing this (haven't really looked into it yet), but I suspect it's a "Travis only" problem.

CommentFileSizeAuthor
#4 panopoly-travis-chrome43-2537902.patch1.19 KBdsnopek

Comments

dsnopek’s picture

Priority: Normal » Critical
Issue tags: +sprint
dsnopek’s picture

The 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...

dsnopek’s picture

I 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...

dsnopek’s picture

Status: Active » Needs review
StatusFileSize
new1.19 KB

Here'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. :-)

  • dsnopek committed d3d0bd0 on 7.x-1.x
    Issue #2537902 by dsnopek: Chrome tests failing on Travis-CI
    
dsnopek’s picture

Status: Needs review » Fixed

I 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

dsnopek’s picture

FYI, 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!

dsnopek’s picture

Supposedly, 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

  • dsnopek committed d3d0bd0 on 8.x-1.x
    Issue #2537902 by dsnopek: Chrome tests failing on Travis-CI
    

  • dsnopek committed d3d0bd0 on 8.x-2.x
    Issue #2537902 by dsnopek: Chrome tests failing on Travis-CI
    

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.