search

jupyter / declarativewidgets

[RETIRED] Jupyter Declarative Widget Extension
http://jupyter.org/declarativewidgets/docs.html
Other
120 stars 38 forks source link

PR builds are failing again... TRAVIS!!!! #517

Closed lbustelo closed 7 years ago

poplav commented 7 years ago

Over the past few days we have been seeing errors such as (note this is not consistent on which libraries will fail from what I can see):

      https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/main-settings/0.13.11/jars/main-settings.jar
        ::::::::::::::::::::::::::::::::::::::::::::::
        ::              FAILED DOWNLOADS            ::
        :: ^ see resolution messages for details  ^ ::
        ::::::::::::::::::::::::::::::::::::::::::::::
        :: org.scala-sbt#main;0.13.11!main.jar
        :: org.scala-sbt#actions;0.13.11!actions.jar
        :: org.scala-sbt#main-settings;0.13.11!main-settings.jar
        :: org.scala-sbt#compiler-interface;0.13.11!compiler-interface.jar
        ::::::::::::::::::::::::::::::::::::::::::::::

This is resulting from the make target: dist/declarativewidgets/static/declarativewidgets.jar This works locally consistently, but errors on Travis. It looks fairly similar to https://github.com/travis-ci/travis-ci/issues/3242, so I am going to open an issue on Travis and see what they say. cc @peller

poplav commented 7 years ago

Was about to open an issue, but it looks like others beat me to it (~a day ago) at https://github.com/travis-ci/travis-ci/issues/6641. Looks like we are not the only ones, so it's not on our end.

poplav commented 7 years ago

Link to https://github.com/sbt/sbt/issues/2758 as well

peller commented 7 years ago

The sbt build started working again this morning. Something to do with HTTPS->HTTP redirects not being allowed, though it's not clear who fixed this or how.

peller commented 7 years ago

phantom is still failing on port 4444 however

peller commented 7 years ago

Chrome on linux seems to have stopped working. Can't find any relevant bug reports, and reverting to older chromedrivers and selenium-standalone versions didn't seem to make any difference, so perhaps it's something else in the environment? It's possible that it's a timing issue and selenium isn't ready?

Switched to use firefox for travis PR tests rather than chrome, for now. 62511c020807b871a1886ff0a384fb22c616ac49

peller commented 7 years ago

There's still an intermittent problem where the R system tests timeout at 60 sec. The initial R system test sometimes takes upwards of 30 seconds (witnessed on my system)

peller commented 7 years ago

Travis is passing at the moment. Both chrome/linux and R issues seem to have gone away.