Unreliable karma tests in Travis #26
Comments
|
I've had success running my tests in multiple browsers during CI with https://saucelabs.com/. Might be worth a shot. |
david-hub024
pushed a commit
to david-hub024/React_VideoPlayer
that referenced
this issue
Dec 23, 2018
Travis’ browser was too unreliable for karma tests Fixes cookpete/react-player#26
david-hub024
pushed a commit
to david-hub024/React_VideoPlayer
that referenced
this issue
May 23, 2020
Travis’ browser was too unreliable for karma tests Fixes cookpete/react-player#26
albanqoku
added a commit
to albanqoku/react-player
that referenced
this issue
Feb 24, 2021
Travis’ browser was too unreliable for karma tests Fixes cookpete/react-player#26
Webmaster1116
added a commit
to Webmaster1116/video-player
that referenced
this issue
May 20, 2021
Travis’ browser was too unreliable for karma tests Fixes cookpete/react-player#26
webmiraclepro
added a commit
to webmiraclepro/video-player
that referenced
this issue
Sep 9, 2022
Travis’ browser was too unreliable for karma tests Fixes cookpete/react-player#26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like the browser inside the Travis CI machines isn't quite good enough to safely test in Travis. See an example build log where one test fails, which I can't reproduce locally. Perhaps in Travis we should revert to just the shallow render tests, and just run
karmatests locally when building/releasing.The text was updated successfully, but these errors were encountered: