search

tarantool / queue

Create task queues, add and take jobs, monitor failed tasks
Other
237 stars 52 forks source link

Travis builds are failing #68

Closed rybakit closed 6 years ago

rybakit commented 6 years ago

https://travis-ci.org/tarantool/queue.

bigbes commented 6 years ago

Everything should be OK, except tests for 1.6 (check for vinyl were broke).

22/22 Test #22: vinyl-090-grant-check.t ..........   Passed    0.37 sec
100% tests passed, 0 tests failed out of 22
Total Test time (real) =  47.50 sec
Built target check
The command "if [ "${TARGET}" = "test" ]; then
    ./test.sh;
else
    git clone https://github.com/packpack/packpack.git packpack;
    packpack/packpack;
fi;
" exited with 0.

store build cache 0.00s, 3.46s

changes detected, packing new archive
uploading archive

Done. Your build exited with 1.

It's strange exit 1, that came out of nowhere

rybakit commented 6 years ago

I've also found

$ git describe --long
fatal: No annotated tags can describe '0ab1f7e4caeaef6d7af7507e6cfe0db41746bf17'.
However, there were unannotated tags: try --tags.
The command "git describe --long" exited with 128.

https://travis-ci.org/tarantool/queue/jobs/319712636#L476-L481

For my personal projects I ended up running tests in docker containers. This way you are safe from this kind of 3d party issues and can run tests on any CI system (I guess most of them support docker nowadays). For example, I run my "docker-powered" tests on Travis CI, Semaphore CI and locally without any modification.

rybakit commented 6 years ago

It's strange exit 1, that came out of nowhere

I think it comes from some error(s) above (maybe the one I pointed out in the previous comment). set -e may work to stop the build on the first error occurrence.

LaserPhaser commented 6 years ago

Fixed by PR #77