Note that there are some explanatory texts on larger screens.

plurals
  1. POGithub - Travis-CI validation fails - Workstation change
    primarykey
    data
    text
    <p>I am actually facing to some strange issue. I am maintaining some Lua projects of mine, hosted at Github. I have recently discovered that it's fairly possible to achieve Lua-Testing with Travis-CI validation service. It simply consists of writing tests specs, to be run with a unit testing library (I am using <a href="http://norman.github.com/telescope/" rel="nofollow">Telescope</a>), and then fool Travis worker, faking Erlang.</p> <p>For instance, I have successfully included Travis in this project: see <a href="https://github.com/Yonaba/30log" rel="nofollow">30log</a> - <a href="https://github.com/Yonaba/30log/blob/master/.travis.yml" rel="nofollow">Travis YAML</a> file here.</p> <p>I'd like to point out that I am using GNU-bash (v1.7.10) on my workstation (running under Windows 7 x86) to commit, and then push on remote repos.</p> <p>Everything went fine. Until I switched to a new workstation (WIndows 7, x64). I basicallly installed Gnu-Bash, then I just copied-paste some files from the previous workstation (that is, <strong>.ssh</strong> folder containing rsa_pub keys, the <strong>.bash_history</strong> file, the global <strong>.gitconfig</strong> file and the <strong>folder containing all my on-going projects sources</strong>) on the new workstation.I made some commits, and I pushed them successfuly. But then any build tests from Travis-CI are now failing, the workers report that some files cannot be found. Here is the <a href="https://travis-ci.org/Yonaba/30log" rel="nofollow">log report from Travis-CI</a>, for instance:</p> <blockquote> <p>Using worker: bluebox-jvm-otp.worker.travis-ci.org:travis-jvm-10 <br/> $ cd ~/builds<br/> $ export LUA=""<br/> $ git clone --branch=master --depth=100 --quiet<br/> git://github.com/Yonaba/30log.git Yonaba/30log<br/> $ cd Yonaba/30log<br/> $ git checkout -qf 0b60646339e65df0f79ce66b6a76c9b825ba5032<br/> $ source ~/otp/R14B04/activate<br/> -bash: /home/travis/otp/R14B04/activate: No such file or directory<br/> Done. Build script exited with: 1<br/></p> </blockquote> <p>The problem is <strong>certainly not related to the code itself</strong>, as <strong>specs tests are all passing fine</strong>, running them with the test suite (Telescope) locally on my workstation. It just seems travis's worker is failing to find some key file to process the new commits correctly, and then reports that fail.</p> <p>Any thoughts about what's going on, and how to fix that issue ? Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload