New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome install is broken on Travis #39

Closed
sjrd opened this Issue Apr 14, 2016 · 1 comment

Comments

Projects
None yet
3 participants

@sjrd sjrd added the bug label Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

@nicolasstucki

This comment has been minimized.

Show comment
Hide comment
@nicolasstucki

nicolasstucki Apr 14, 2016

Contributor

It looks like the latest release of google-chrome-stable requires updates on libstdc++6 and lsb-base

Unpacking google-chrome-stable (from google-chrome-stable_current_amd64.deb) ...
dpkg: dependency problems prevent configuration of google-chrome-stable:
 google-chrome-stable depends on libstdc++6 (>= 4.8.0); however:
  Version of libstdc++6 on system is 4.6.3-1ubuntu5.
 google-chrome-stable depends on lsb-base (>= 4.1); however:
  Version of lsb-base on system is 4.0-0ubuntu20.3.
dpkg: error processing google-chrome-stable (--install):
 dependency problems - leaving unconfigured
Contributor

nicolasstucki commented Apr 14, 2016

It looks like the latest release of google-chrome-stable requires updates on libstdc++6 and lsb-base

Unpacking google-chrome-stable (from google-chrome-stable_current_amd64.deb) ...
dpkg: dependency problems prevent configuration of google-chrome-stable:
 google-chrome-stable depends on libstdc++6 (>= 4.8.0); however:
  Version of libstdc++6 on system is 4.6.3-1ubuntu5.
 google-chrome-stable depends on lsb-base (>= 4.1); however:
  Version of lsb-base on system is 4.0-0ubuntu20.3.
dpkg: error processing google-chrome-stable (--install):
 dependency problems - leaving unconfigured

@nicolasstucki nicolasstucki self-assigned this Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 14, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 15, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 15, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 15, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 15, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 19, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 19, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 19, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 19, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Apr 19, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Jun 9, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Jun 9, 2016

nicolasstucki added a commit to nicolasstucki/scala-js-env-selenium that referenced this issue Jun 9, 2016

@nicolasstucki nicolasstucki removed their assignment Feb 20, 2017

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

As a side effect, this fixes scala-js#39.

@gzm0 gzm0 self-assigned this Jul 27, 2017

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

As a side effect, this fixes scala-js#39.

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

As a side effect, this fixes scala-js#39.

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

This fixes scala-js#39 (chrome on ci) and scala-js#62 (use gecko driver).

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

This fixes scala-js#39 (chrome on ci) and scala-js#62 (use gecko driver).

gzm0 added a commit to gzm0/scala-js-env-selenium that referenced this issue Jul 27, 2017

Fix CI
Note: This removes the keepAlive tests: The are too expensive for what
they are worth. Relying on killall to determine that there are no
processes around is too fragile. We should replace these tests by
unit-tests (scala-js#67).

This fixes scala-js#39 (chrome on ci) and scala-js#62 (use gecko driver).

@sjrd sjrd closed this in 06d6877 Jul 27, 2017

@gzm0 gzm0 modified the milestone: v0.2.0 Jul 29, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment