Skip to content
This repository was archived by the owner on Oct 19, 2018. It is now read-only.
This repository was archived by the owner on Oct 19, 2018. It is now read-only.

Travis failures - bad config #221

Description

@sfcgeorge

Looks like Travis has been partly failing for a while. This isn't ideal as you can quickly spiral into ignoring more and more errors until the whole test suite is broken and you're merging blind.

One issue seems to be missing jRuby binary.

The other issue is missing PhantomJS download, for an ancient version.

As per #201 we should stop supporting ancient versions of Ruby / jRuby / PhantomJS, aka just delete those Travis configs. Currently Travis only tests up to Ruby 2.1 so it would be good to add 2.4 to the matrix.

Activity

  1. added this to the Release 0.15 milestone on Nov 15, 2017
  2. janbiedermann commented on Nov 20, 2017

    @janbiedermann
    Contributor

    most of this is done in sachsenring, yet travis config needs to be updated to use -pre gems
    we use chromes headless driver to drive the test.

  3. janbiedermann commented on Feb 12, 2018

    @janbiedermann
    Contributor

    Travis is absolutely useless for this project. Tests are completely unreliable and subtle versions changes result in failures ONLY ON TRAVIS. I guess that is, because they only provide ancient dinosaur software, where various bugs, long ago fixed in modern of versions of that basic software, are present all over the place.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions