why my ci-build stay pending?

Question

why my ci-build stay pending?

epiphyllum opened this issue 10 years ago · 3 comments

but the log shows that: the runner consistently ask for new builds?

Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:50:42 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:50:47 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:50:52 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:50:57 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:02 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:07 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:12 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:17 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:22 +0800
Started POST "/api/v1/builds/register.json" for 127.0.0.1 at 2015-04-09 17:51:27 +0800

Answer 1 · 2015-04-09T09:53:11.000Z

epiphyllum commented 10 years ago

Answer 2 · 2015-04-09T09:55:32.000Z

@epiphyllum the gitlab-ci-runner polls the gitlab-ci server for builds. That is how the gitlab-ci-runner is implemented.

Answer 3 · 2015-04-09T09:55:42.000Z

the netwok is too slow. sorry for the issue