Always got failed status without executing my job script

Env:

• OS X 10.10.4
• gitlab-ci-multi-runner 0.3.3 (dbaf96f)

The same build is OK on Ubuntu 14.04, but always got failed on my mbp, the output like this:

gitlab-ci-multi-runner 0.3.3 (dbaf96f)
Using Shell executor...
Running on T-mbp02...
Fetching changes...

Build failed with exit status 1

My Job Script:

env
set -x
echo 'hello wold~'
exit 0

Even if only had the echo cmd, I could find nothing in the output log.

Here's some output when I run gitlab-ci-multi-runner --debug run :

INFO[0006] d97216e8 Checking for builds... received     
DEBU[0006] 0 Received new build for d97216e8 build 18   
DEBU[0006] 1 Added a new build &{{18 9 env
set -x
echo 'hello wold~'
exit
=======blablabla==========
true 1800}  0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0  0x208816180   0x208800870 0 concurrent-0 0 runner-d97216e8-concurrent-0 0 runner-d97216e8-project-9-concurrent-0 {[] 0 [0 0 0 0] [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] 0} {{0 0} 0 0 0 0}} 
INFO[0006] d97216e8 18 gitlab-ci-multi-runner 0.3.3 (dbaf96f) 
======blablabla============
105 116 10 108 115 32 45 108 97 10 101 99 104 111 32 39 104 101 108 108 111 32 119 111 108 100 126 39] bash [--login] false } 
INFO[0006] d97216e8 18 Using Shell executor...          
DEBU[0006] d97216e8 18 Starting shell command...        
DEBU[0006] d97216e8 18 Waiting for signals...           
DEBU[0006] d97216e8 18 Build took 183.370367ms          
DEBU[0006] d97216e8 18 Waiting for build log updater to finish 
DEBU[0006] d97216e8 18 Build log updater finished.      
DEBU[0006] d97216e8 18 updateBuildLog Received finish.  
DEBU[0006] d97216e8 18 PushTrace finished               
INFO[0006] d97216e8 18 Submitting build to coordinator... ok 
INFO[0006] d97216e8 18 Build finished.                  
DEBU[0006] d97216e8 18 ReadTrace finished               
=============blablabla=================
 true 1800} failed 2015-05-20 23:32:33.279022686 +0800 CST 2015-05-20 23:32:33.462393053 +0800 CST 183.370367ms 
Build failed with exit status 1 0x208816180

Anyone help?

Do you have git installed?

@ayufan Yes, git is installed.

More test results:

1. Jenkins and Buildkite runner is working well on this mac.
2. gitlab-ci-multi-runner is working well on another mac with OS X 10.10.3 with almost same env (inited by same script).

Hi all,

I got the same error on mac with OS X 10.10.3.

It breaks on the git clone/fetch with "Build failed with exit status 1" error.

I have the same project/job been run by other runners on a Xubuntu VM and it runs as expected.

Thanks

I can confirm this issue. @ayufan I wrote about it to slack.

Hi @vsizov , on which slack team you are talking about this? Can I join?

Probably the GitLab team one...

I might want to note that something like that happens to me as well, but I can't really read the debug output so I was hoping for those new commits. Problem is that the ci build failed and therefore there's no new version to test 0.4.0.pre :/

I pushed to dev new version with better debug logging. There you will find script that is executed by the runner. If you could try that script.

gitlab-ci-multi-runner --debug run

Milestone changed to v0.4.0

@ayufan You might want to consider to translate \n and \r\n in the debug output as well so that someone can easily read over the script and not some endlessly long string, and of course maybe strip out sensitive information from the output

PS: I didn't feel like creating a issue for this very small suggestion and since you were mentioning the debug output here~

@neico build output is much more readable in latest bleeding edge

Please try latest Bleeding Edge release. It should fix the problem.

finally, it works! :) yay!

Thanks for verification @vsizov!

Status changed to closed

mentioned in issue #2283 (closed)