travis-ci

Karma Start Fails - HeadlessChrome - ERROR Uncaught [object Object]

落花浮王杯 提交于 2019-12-18 15:07:14
问题 I am using Karma to run test on my Angular 4 app. It works locally but when it runs on my host environment (Travis CI) it fails with the following information: INFO [HeadlessChrome 0.0.0 (Ubuntu 0.0.0)]: Connected on socket vT0QnQaqRkn010dfsw with id 10189531 HeadlessChrome 0.0.0 (Ubuntu 0.0.0): Executed 0 of 180 SUCCESS (0 secs / 0 secs) e 0.0.0 (Ubuntu 0.0.0): Executed 1 of 180 SUCCESS (0 secs / 0.714 secs) HeadlessChrome 0.0.0 (Ubuntu 0.0.0) ERROR Uncaught [object Object] at http:/

Get Travis Shield on Github to Reflect Selected Branch Status

早过忘川 提交于 2019-12-18 12:34:10
问题 Right now I can get my travis shield to either reflect the latest run, or a specific branch, irrespective of what branch I select in my github project page. I can do this by either leaving out or specifying the branch name at the end of the URL. Instead, I would like to get the shield corresponding to the selected branch. In other words, each time I select a different branch, the URL to the travis shield in my README.md file would change. In SVN you could use SVN keywords to implement

Using R package source files in packrat (rather than CRAN) with Travis-CI

半腔热情 提交于 2019-12-18 12:01:17
问题 I'm working with an R package that is an RStudio project, and I'm using packrat to keep a local copy of the source of the packages I depend on for my project. I've got Travis-CI checking my R package each time I make a commit, but each time Travis builds my package it gets the latest version of the dependent packages, rather than the versions I've got in my packrat/ directory. I can see in richfitz/wood that he appears to have achieved this goal with this in his .travis.yml file: env: USE

Using R package source files in packrat (rather than CRAN) with Travis-CI

。_饼干妹妹 提交于 2019-12-18 12:00:38
问题 I'm working with an R package that is an RStudio project, and I'm using packrat to keep a local copy of the source of the packages I depend on for my project. I've got Travis-CI checking my R package each time I make a commit, but each time Travis builds my package it gets the latest version of the dependent packages, rather than the versions I've got in my packrat/ directory. I can see in richfitz/wood that he appears to have achieved this goal with this in his .travis.yml file: env: USE

How to ensure that README.rst is valid?

空扰寡人 提交于 2019-12-17 19:23:52
问题 There are two version of my little tool: https://pypi.python.org/pypi/tbzuploader/2017.11.0 https://pypi.python.org/pypi/tbzuploader/2017.12.0 Bug: The pypi page looks ugly. In the last update a change in README.rst cases a warning: user@host> rst2html.py README.rst > /tmp/foo.html README.rst:18: (WARNING/2) Inline emphasis start-string without end-string. README.rst:18: (WARNING/2) Inline emphasis start-string without end-string. Now the pypi page looks ugly :-( I use this recipe to do CI,

apt-get update fails with 404 in a previously working build

爱⌒轻易说出口 提交于 2019-12-17 09:59:32
问题 I am running a Travis build and it fails when building the mysql:5.7.27 docker image. The Dockerfile runs apt-get update and then I get an error W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found . Using curl I can see it is redirecting, but the redirect-to URL results in a 404. Has anyone seen this sort of behaviour and have a remedy? Is it basically unfixable until debian makes changes? ➜ ms git:(develop) curl --head http://deb

apt-get update fails with 404 in a previously working build

。_饼干妹妹 提交于 2019-12-17 09:59:04
问题 I am running a Travis build and it fails when building the mysql:5.7.27 docker image. The Dockerfile runs apt-get update and then I get an error W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found . Using curl I can see it is redirecting, but the redirect-to URL results in a 404. Has anyone seen this sort of behaviour and have a remedy? Is it basically unfixable until debian makes changes? ➜ ms git:(develop) curl --head http://deb

Travis build getting Errored randomly due to timeout/authentication failure

爱⌒轻易说出口 提交于 2019-12-14 02:35:07
问题 Travis builds are failing randomly due to problems like connection timeout, authentication failure etc. Any idea why is it happening ? How it can be fixed? Check this build, two of the jobs passed while other two failed. Here in this build , all the jobs failed. Here is my composer.json, if it can give any clue. 回答1: The problem is caused by limits on GitHub API usage. Travis adds own authentication token, but in case there are many projects building, the limit of 5000 API requests in hour is

Choose a specific Ubuntu version

China☆狼群 提交于 2019-12-14 00:54:59
问题 If i'm using the default travis file it looks like that the build machine is Ubuntu Precise. Hit http://ppa.launchpad.net precise Release.gpg Is there any tweak to use an trusty or utopic machine? 回答1: This is now implemented, add to .travis.yml : dist: trusty to use ubuntu trusty. 回答2: No. Only Precise. Works are ongoing re Trusty. https://github.com/travis-ci/travis-ci/issues/2046 来源: https://stackoverflow.com/questions/29806296/choose-a-specific-ubuntu-version

My Travis keeps erroring

一世执手 提交于 2019-12-13 20:40:38
问题 All tests are passing, but in in the end, it gives The command "make html" failed and exited with 2 during . This happens since I started using cache. Initially I just had cache: apt: true directories: - $HOME/virtualenv/python2.7/lib/python2.7/site-packages - node_modules in travis.yml but I also added - $HOME/virtualenv/bin and cleared my cache in master branch before I ran another build. It passed once, but then keeps failing. I cleared the cache multiple times but no avail. 来源: https:/