Travis is downloading older Chrome versions in place of chrome: stable

Travis CI Discussions & Feedback
1

Suddenly today (approx 25 minutes ago) our builds started to download an older version of chrome. This causes chrome driver to fail.

We are using the following in our .travis.yml
addons:
chrome: stable

This had been working fine:
Before:
https://travis-ci.com/infor-design/enterprise/jobs/232840997#L517

Now:
https://travis-ci.com/infor-design/enterprise/jobs/233764514#L492

Is this being worked on or is it an unknown problem or change needed in our config? The issue is that this fails all the tests now.

https://travis-ci.com/infor-design/enterprise/jobs/233757159#L585

Im not sure if this is related but if i try manually installing chrome i get this error: https://travis-ci.com/infor-design/enterprise/jobs/233773743#L1709

Any Suggestions Please? We are totally stuck now.

2 Likes
2

Iā€™m seeing the same, and having the same issue with Chromedriver.

3

First, you are downloading chrome: beta in the failing job. (https://travis-ci.com/infor-design/enterprise/jobs/233764514/config)

Second, https://travis-ci.com/infor-design/enterprise/jobs/233764514#L424 (I actually found it by searching the raw log for ā€œchromeā€):

dpkg-deb: error: archive ā€˜/tmp/google-chrome-beta_current_amd64.debā€™ has premature member ā€˜control.tar.xzā€™ before ā€˜control.tar.gzā€™, giving up

Means that dpkg cannot understand the packageā€™s format.
Since xz is a newer format than gz, this most likely means that dpkg is too old.
I.e. that Google has dropped Trusty support in its Chrome .deb packages, and you need to migrate to Xenial or Bionic.

The Chrome version that you see further on is presumably a preinstalled one.

2 Likes
4

Iā€™m trying to get confirmation (e.g. from Google) but I believe @native-api is right: Google has dropped Trusty support for Chrome with the latest release today.

As mentioned, the best suggestion would be to try to run your builds on Xenial instead with

dist: xenial

in your .travis.yml file.

3 Likes
5

Thanks @dominic and @native-api. Using xenial seems to work. I only needed to change

dist: trusty to dist: xenail

Two follow up questions:

  1. Any problem using this on our open source builds? I see this from that reference page link:

Please note that Xenial is available on our hosted fully virtualized infrastructure. If you are running an Enterprise installation, please reach out to enterprise@travis-ci.com to see how you can use the Xenial Docker images.

  1. Is there a VM that that mimics this for docker https://hub.docker.com/u/travisci/ i should use? We need this for visual image regression tests when creating them for development.

Thanks

6

@tmcconechy Glad to hear switching to Xenial helped. Here are the answers to your questions:

  1. You can definitely use Xenial for your open source builds on both travis-ci.org and travis-ci.com. This is what we mean when we say ā€œour hosted fully virtualized infrastructureā€. In fact, itā€™s now the default distribution too: https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment.

  2. Since we donā€™t have a container-based infrastructure anymore, we unfortunately donā€™t provide equivalent Docker containers like we did in the past. If it helps, you have the option to connect directly to the VM using our debug mode feature. Take note that this needs to be enabled manually by us for open source repositories. Just reach out to support [AT] travis-ci [DOT] com if needed.

Hope this helps!

1 Like