Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi Tang, I thought I replied about this earlier. There seems to be a regression running jobs directly on master, at least for newer versions of Jenkins. Running on a slave does work. Ramy From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Monday, July 27, 2015 6:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi Zaro, On 07/24/2015 11:44 PM, Zaro wrote: Tang, Have you tried to look at the function registrations and gearman queue on the gearman server as i suggested? The instructions are in the wiki i referenced (in 'Starting the gearman workers' section). What you are seeing from the gear_client could also be from passing in a function name that does not exist. Unfortunately the simple gear_client does not check whether the passed in functions are valid so what you want to do is verify that the gearman functions have been registered by using the 'workers' command. Thank you for your suggestion. I have not seen the inside of Gearman. But I set up a slave node, and the job can run on the slave node. This is also acceptable for me. So I think I have to go on with my work first. And I'll check what you said later. Thanks very much. :) On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote: On 07/24/2015 03:36 PM, Tang Chen wrote: Hi Zaro, Thanks to reply. On 07/24/2015 03:06 PM, Zaro wrote: That is correctly, the Jenkins UI will not show any info about the gearman queue. If job is pending in Jenkins that means it's been added to the gearman queue and has been moved to the jenkins build queue. The jenkins UI will only show the job once it's in the jenkins queue. Hmm. What happens when you manually start a build by click on the build icon in the jenkins UI? If I click the build icon in the jenkins UI, the job can run. Wired, isn't it ? Thanks. I'm wondering if maybe your labels are configured correctly for your jobs and slaves. Are there any labels on the job or the nodes (master or slaves)? I think the jobs would be in a pending state if there are labels on nodes and jobs but they do not match. I would check to see if there are any labels on the jobs and if there are then I would remove all of the labels and try again. There are step by step directions on how to setup the gearman-plugin in the jenkins wiki[1] which also shows you how to debug by viewing the gearman server queue and function registrations. Try to make sure the functions are registered correctly and that the job is in the queue after you run the gear-client command. A couple of questions: What version of Jenkins are you running? I think openstack runs on 1.565.3 Also I don't think we've ever tested Jenkins and the gearman server running on the same machine or VM. Maybe one thing you can try is to run them on separate VMs? I don't have any label, and only a master, no slave. My jenkins is 1.609.1. The whole problem is described here: http://paste.openstack.org/show/405051/ Please help to check and see. BTW, I post the problem to #openstack-infra IRC channel. You can join into that meeting if you'd like to. Thanks. [1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi Zaro, On 07/24/2015 11:44 PM, Zaro wrote: Tang, Have you tried to look at the function registrations and gearman queue on the gearman server as i suggested? The instructions are in the wiki i referenced (in 'Starting the gearman workers' section). What you are seeing from the gear_client could also be from passing in a function name that does not exist. Unfortunately the simple gear_client does not check whether the passed in functions are valid so what you want to do is verify that the gearman functions have been registered by using the 'workers' command. Thank you for your suggestion. I have not seen the inside of Gearman. But I set up a slave node, and the job can run on the slave node. This is also acceptable for me. So I think I have to go on with my work first. And I'll check what you said later. Thanks very much. :) On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen tangc...@cn.fujitsu.com mailto:tangc...@cn.fujitsu.com wrote: On 07/24/2015 03:36 PM, Tang Chen wrote: Hi Zaro, Thanks to reply. On 07/24/2015 03:06 PM, Zaro wrote: That is correctly, the Jenkins UI will not show any info about the gearman queue. If job is pending in Jenkins that means it's been added to the gearman queue and has been moved to the jenkins build queue. The jenkins UI will only show the job once it's in the jenkins queue. Hmm. What happens when you manually start a build by click on the build icon in the jenkins UI? If I click the build icon in the jenkins UI, the job can run. Wired, isn't it ? Thanks. I'm wondering if maybe your labels are configured correctly for your jobs and slaves. Are there any labels on the job or the nodes (master or slaves)? I think the jobs would be in a pending state if there are labels on nodes and jobs but they do not match. I would check to see if there are any labels on the jobs and if there are then I would remove all of the labels and try again. There are step by step directions on how to setup the gearman-plugin in the jenkins wiki[1] which also shows you how to debug by viewing the gearman server queue and function registrations. Try to make sure the functions are registered correctly and that the job is in the queue after you run the gear-client command. A couple of questions: What version of Jenkins are you running? I think openstack runs on 1.565.3 Also I don't think we've ever tested Jenkins and the gearman server running on the same machine or VM. Maybe one thing you can try is to run them on separate VMs? I don't have any label, and only a master, no slave. My jenkins is 1.609.1. The whole problem is described here: http://paste.openstack.org/show/405051/ Please help to check and see. BTW, I post the problem to #openstack-infra IRC channel. You can join into that meeting if you'd like to. Thanks. [1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
On 07/24/2015 12:59 PM, Zaro wrote:
Hello Tang, Openstack slaves only have a single executor so what you
are probably seeing is due to using build slaves that have multiple
executors. There were a few bugs[1] that was fixed recently around
these types of deadlock issues. The new gearman-plugin release[2]
contains fixes for those issues. Also if you want to test the
gearman-plugin with Jenkins independently of zuul you can use the
simple gearman-plugin-client[3] to send jobs your gearman server to
see if the jobs get built.
[1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
https://issues.jenkins-ci.org/browse/JENKINS-25867
[2]
http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
[3] https://github.com/zaro0508/gearman-plugin-client
Hi Zaro,
Thanks for the reply.
But I updated the gearman plugin to 0.1.2, and used the
gearman-plugin-client to submit jobs.
# python gear_client.py -s localhost
--function=build:noop-check-communication
Sat Jul 25 14:16:57 2015
Sending job: build:noop-check-communication to localhost with
params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid':
'08ad7a195237493d91eea55789e76128'}
Waiting for jobs to finish.
It doesn't work. The job submitted by the client is also pending.
BTW, I cannot see the job submitted by client in my Jenkins GUI. Is that
correct ?
Thanks.
-Khai
On Thu, Jul 23, 2015 at 9:13 PM, Tang Chen tangc...@cn.fujitsu.com
mailto:tangc...@cn.fujitsu.com wrote:
On 07/24/2015 12:00 PM, Tang Chen wrote:
On 07/24/2015 10:08 AM, Tang Chen wrote:
On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
Are you running on 'master' nodes? I remember seeing
an issue where with a recent version of Jenkins or a
plugin where it doesn't execute jobs on the master node.
But when run on non-master jenkins slaves, it works fine.
I checked my configuration, and made sure these things:
1. I have only a master node, no slave node.
2. I have 20 idle executors on master node.
3. My master node is online.
4. My master node is set to Utilize this node as much as
possible.
5. zuul is able to be notified by Gerrit, and tell Jenkins
to start jobs.
But the jobs are always pending.
And my Gearman reports this error sometimes.
2015-07-25 10:50:44,914 ERROR gear.Server: Exception in poll loop:
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/gear/__init__.py,
line 2614, in _doPollLoop
self._pollLoop()
File
/usr/local/lib/python2.7/dist-packages/gear/__init__.py,
line 2626, in _pollLoop
ret = self.poll.poll()
IOError: [Errno 4] Interrupted system call
Not sure if it has anything to do with this problem.
In Jenkins GUI, Gearman connection is tested successfully on
127.0.0.1:4730 http://127.0.0.1:4730.
Seeing from zuul debug log, Gearman has successfully submitted the
jobs.
2015-07-25 11:42:09,255 DEBUG zuul.Scheduler: Adding trigger
event: TriggerEvent patchset-created openstack-dev/sandbox master
205360,1
2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Done adding trigger
event: TriggerEvent patchset-created openstack-dev/sandbox master
205360,1
2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Run handler awake
2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Fetching trigger event
2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Processing trigger
event TriggerEvent patchset-created openstack-dev/sandbox master
205360,1
2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
Event TriggerEvent patchset-created openstack-dev/sandbox master
205360,1 for change Change 0x7ff518312c10 205360,1 matched
EventFilter types: patchset-created in pipeline
IndependentPipelineManager check
2015-07-25 11:42:09,257 INFO zuul.Scheduler: Adding
openstack-dev/sandbox, Change 0x7ff518312c10 205360,1 to
Pipeline check
2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
Considering adding change Change 0x7ff518312c10 205360,1
2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
Checking for changes needed by Change 0x7ff518312c10 205360,1:
2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
No changes needed
2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
Adding change Change 0x7ff518312c10 205360,1 to queue
ChangeQueue check: openstack-dev/sandbox
2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager:
Event TriggerEvent patchset-created openstack-dev/sandbox master
205360,1 for change Change 0x7ff518312c10 205360,1 matched
EventFilter types: patchset-created in pipeline
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
That is correctly, the Jenkins UI will not show any info about the gearman
queue. If job is pending in Jenkins that means it's been added to the
gearman queue and has been moved to the jenkins build queue. The jenkins
UI will only show the job once it's in the jenkins queue.
Hmm. What happens when you manually start a build by click on the build
icon in the jenkins UI? I'm wondering if maybe your labels are configured
correctly for your jobs and slaves. Are there any labels on the job or the
nodes (master or slaves)? I think the jobs would be in a pending state if
there are labels on nodes and jobs but they do not match. I would check to
see if there are any labels on the jobs and if there are then I would
remove all of the labels and try again. There are step by step directions
on how to setup the gearman-plugin in the jenkins wiki[1] which also shows
you how to debug by viewing the gearman server queue and function
registrations. Try to make sure the functions are registered correctly and
that the job is in the queue after you run the gear-client command.
A couple of questions:
What version of Jenkins are you running? I think openstack runs on 1.565.3
Also I don't think we've ever tested Jenkins and the gearman server running
on the same machine or VM. Maybe one thing you can try is to run them on
separate VMs?
[1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
On Thu, Jul 23, 2015 at 11:20 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/24/2015 12:59 PM, Zaro wrote:
Hello Tang, Openstack slaves only have a single executor so what you
are probably seeing is due to using build slaves that have multiple
executors. There were a few bugs[1] that was fixed recently around these
types of deadlock issues. The new gearman-plugin release[2] contains
fixes for those issues. Also if you want to test the gearman-plugin with
Jenkins independently of zuul you can use the simple
gearman-plugin-client[3] to send jobs your gearman server to see if the
jobs get built.
[1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
https://issues.jenkins-ci.org/browse/JENKINS-25867
[2]
http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
[3] https://github.com/zaro0508/gearman-plugin-client
Hi Zaro,
Thanks for the reply.
But I updated the gearman plugin to 0.1.2, and used the
gearman-plugin-client to submit jobs.
# python gear_client.py -s localhost
--function=build:noop-check-communication
Sat Jul 25 14:16:57 2015
Sending job: build:noop-check-communication to localhost with
params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid':
'08ad7a195237493d91eea55789e76128'}
Waiting for jobs to finish.
It doesn't work. The job submitted by the client is also pending.
BTW, I cannot see the job submitted by client in my Jenkins GUI. Is that
correct ?
Thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi Zaro,
Thanks to reply.
On 07/24/2015 03:06 PM, Zaro wrote:
That is correctly, the Jenkins UI will not show any info about the
gearman queue. If job is pending in Jenkins that means it's been
added to the gearman queue and has been moved to the jenkins build
queue. The jenkins UI will only show the job once it's in the jenkins
queue.
Hmm. What happens when you manually start a build by click on the
build icon in the jenkins UI? I'm wondering if maybe your labels are
configured correctly for your jobs and slaves. Are there any labels
on the job or the nodes (master or slaves)? I think the jobs would be
in a pending state if there are labels on nodes and jobs but they do
not match. I would check to see if there are any labels on the jobs
and if there are then I would remove all of the labels and try again.
There are step by step directions on how to setup the gearman-plugin
in the jenkins wiki[1] which also shows you how to debug by viewing
the gearman server queue and function registrations. Try to make sure
the functions are registered correctly and that the job is in the
queue after you run the gear-client command.
A couple of questions:
What version of Jenkins are you running? I think openstack runs on
1.565.3
Also I don't think we've ever tested Jenkins and the gearman server
running on the same machine or VM. Maybe one thing you can try is to
run them on separate VMs?
I don't have any label, and only a master, no slave.
My jenkins is 1.609.1.
The whole problem is described here:
http://paste.openstack.org/show/405051/
Please help to check and see.
BTW, I post the problem to #openstack-infra IRC channel. You can join
into that meeting if you'd like to.
Thanks.
[1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
On Thu, Jul 23, 2015 at 11:20 PM, Tang Chen tangc...@cn.fujitsu.com
mailto:tangc...@cn.fujitsu.com wrote:
On 07/24/2015 12:59 PM, Zaro wrote:
Hello Tang, Openstack slaves only have a single executor so what
you are probably seeing is due to using build slaves that have
multiple executors. There were a few bugs[1] that was fixed
recently around these types of deadlock issues. The new
gearman-plugin release[2] contains fixes for those issues. Also
if you want to test the gearman-plugin with Jenkins independently
of zuul you can use the simple gearman-plugin-client[3] to send
jobs your gearman server to see if the jobs get built.
[1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
https://issues.jenkins-ci.org/browse/JENKINS-25867
[2]
http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
[3] https://github.com/zaro0508/gearman-plugin-client
Hi Zaro,
Thanks for the reply.
But I updated the gearman plugin to 0.1.2, and used the
gearman-plugin-client to submit jobs.
# python gear_client.py -s localhost
--function=build:noop-check-communication
Sat Jul 25 14:16:57 2015
Sending job: build:noop-check-communication to localhost with
params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid':
'08ad7a195237493d91eea55789e76128'}
Waiting for jobs to finish.
It doesn't work. The job submitted by the client is also pending.
BTW, I cannot see the job submitted by client in my Jenkins GUI.
Is that correct ?
Thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
On 07/24/2015 03:36 PM, Tang Chen wrote:
Hi Zaro,
Thanks to reply.
On 07/24/2015 03:06 PM, Zaro wrote:
That is correctly, the Jenkins UI will not show any info about the
gearman queue. If job is pending in Jenkins that means it's been
added to the gearman queue and has been moved to the jenkins build
queue. The jenkins UI will only show the job once it's in the
jenkins queue.
Hmm. What happens when you manually start a build by click on the
build icon in the jenkins UI?
If I click the build icon in the jenkins UI, the job can run. Wired,
isn't it ?
Thanks.
I'm wondering if maybe your labels are configured correctly for your
jobs and slaves. Are there any labels on the job or the nodes
(master or slaves)? I think the jobs would be in a pending state if
there are labels on nodes and jobs but they do not match. I would
check to see if there are any labels on the jobs and if there are
then I would remove all of the labels and try again. There are step
by step directions on how to setup the gearman-plugin in the jenkins
wiki[1] which also shows you how to debug by viewing the gearman
server queue and function registrations. Try to make sure the
functions are registered correctly and that the job is in the queue
after you run the gear-client command.
A couple of questions:
What version of Jenkins are you running? I think openstack runs on
1.565.3
Also I don't think we've ever tested Jenkins and the gearman server
running on the same machine or VM. Maybe one thing you can try is to
run them on separate VMs?
I don't have any label, and only a master, no slave.
My jenkins is 1.609.1.
The whole problem is described here:
http://paste.openstack.org/show/405051/
Please help to check and see.
BTW, I post the problem to #openstack-infra IRC channel. You can join
into that meeting if you'd like to.
Thanks.
[1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
On Thu, Jul 23, 2015 at 11:20 PM, Tang Chen tangc...@cn.fujitsu.com
mailto:tangc...@cn.fujitsu.com wrote:
On 07/24/2015 12:59 PM, Zaro wrote:
Hello Tang, Openstack slaves only have a single executor so
what you are probably seeing is due to using build slaves that
have multiple executors. There were a few bugs[1] that was
fixed recently around these types of deadlock issues. The new
gearman-plugin release[2] contains fixes for those issues. Also
if you want to test the gearman-plugin with Jenkins
independently of zuul you can use the simple
gearman-plugin-client[3] to send jobs your gearman server to see
if the jobs get built.
[1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
https://issues.jenkins-ci.org/browse/JENKINS-25867
[2]
http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
[3] https://github.com/zaro0508/gearman-plugin-client
Hi Zaro,
Thanks for the reply.
But I updated the gearman plugin to 0.1.2, and used the
gearman-plugin-client to submit jobs.
# python gear_client.py -s localhost
--function=build:noop-check-communication
Sat Jul 25 14:16:57 2015
Sending job: build:noop-check-communication to localhost with
params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid':
'08ad7a195237493d91eea55789e76128'}
Waiting for jobs to finish.
It doesn't work. The job submitted by the client is also pending.
BTW, I cannot see the job submitted by client in my Jenkins GUI.
Is that correct ?
Thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Tang, Have you tried to look at the function registrations and gearman queue on the gearman server as i suggested? The instructions are in the wiki i referenced (in 'Starting the gearman workers' section). What you are seeing from the gear_client could also be from passing in a function name that does not exist. Unfortunately the simple gear_client does not check whether the passed in functions are valid so what you want to do is verify that the gearman functions have been registered by using the 'workers' command. On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen tangc...@cn.fujitsu.com wrote: On 07/24/2015 03:36 PM, Tang Chen wrote: Hi Zaro, Thanks to reply. On 07/24/2015 03:06 PM, Zaro wrote: That is correctly, the Jenkins UI will not show any info about the gearman queue. If job is pending in Jenkins that means it's been added to the gearman queue and has been moved to the jenkins build queue. The jenkins UI will only show the job once it's in the jenkins queue. Hmm. What happens when you manually start a build by click on the build icon in the jenkins UI? If I click the build icon in the jenkins UI, the job can run. Wired, isn't it ? Thanks. I'm wondering if maybe your labels are configured correctly for your jobs and slaves. Are there any labels on the job or the nodes (master or slaves)? I think the jobs would be in a pending state if there are labels on nodes and jobs but they do not match. I would check to see if there are any labels on the jobs and if there are then I would remove all of the labels and try again. There are step by step directions on how to setup the gearman-plugin in the jenkins wiki[1] which also shows you how to debug by viewing the gearman server queue and function registrations. Try to make sure the functions are registered correctly and that the job is in the queue after you run the gear-client command. A couple of questions: What version of Jenkins are you running? I think openstack runs on 1.565.3 Also I don't think we've ever tested Jenkins and the gearman server running on the same machine or VM. Maybe one thing you can try is to run them on separate VMs? I don't have any label, and only a master, no slave. My jenkins is 1.609.1. The whole problem is described here: http://paste.openstack.org/show/405051/ Please help to check and see. BTW, I post the problem to #openstack-infra IRC channel. You can join into that meeting if you'd like to. Thanks. [1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hello Tang, Openstack slaves only have a single executor so what you are probably seeing is due to using build slaves that have multiple executors. There were a few bugs[1] that was fixed recently around these types of deadlock issues. The new gearman-plugin release[2] contains fixes for those issues. Also if you want to test the gearman-plugin with Jenkins independently of zuul you can use the simple gearman-plugin-client[3] to send jobs your gearman server to see if the jobs get built. [1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and https://issues.jenkins-ci.org/browse/JENKINS-25867 [2] http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/ [3] https://github.com/zaro0508/gearman-plugin-client -Khai On Thu, Jul 23, 2015 at 9:13 PM, Tang Chen tangc...@cn.fujitsu.com wrote: On 07/24/2015 12:00 PM, Tang Chen wrote: On 07/24/2015 10:08 AM, Tang Chen wrote: On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine. I checked my configuration, and made sure these things: 1. I have only a master node, no slave node. 2. I have 20 idle executors on master node. 3. My master node is online. 4. My master node is set to Utilize this node as much as possible. 5. zuul is able to be notified by Gerrit, and tell Jenkins to start jobs. But the jobs are always pending. And my Gearman reports this error sometimes. 2015-07-25 10:50:44,914 ERROR gear.Server: Exception in poll loop: Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/gear/__init__.py, line 2614, in _doPollLoop self._pollLoop() File /usr/local/lib/python2.7/dist-packages/gear/__init__.py, line 2626, in _pollLoop ret = self.poll.poll() IOError: [Errno 4] Interrupted system call Not sure if it has anything to do with this problem. In Jenkins GUI, Gearman connection is tested successfully on 127.0.0.1:4730. Seeing from zuul debug log, Gearman has successfully submitted the jobs. 2015-07-25 11:42:09,255 DEBUG zuul.Scheduler: Adding trigger event: TriggerEvent patchset-created openstack-dev/sandbox master 205360,1 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Done adding trigger event: TriggerEvent patchset-created openstack-dev/sandbox master 205360,1 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Run handler awake 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Fetching trigger event 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Processing trigger event TriggerEvent patchset-created openstack-dev/sandbox master 205360,1 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Event TriggerEvent patchset-created openstack-dev/sandbox master 205360,1 for change Change 0x7ff518312c10 205360,1 matched EventFilter types: patchset-created in pipeline IndependentPipelineManager check 2015-07-25 11:42:09,257 INFO zuul.Scheduler: Adding openstack-dev/sandbox, Change 0x7ff518312c10 205360,1 to Pipeline check 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Considering adding change Change 0x7ff518312c10 205360,1 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Checking for changes needed by Change 0x7ff518312c10 205360,1: 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: No changes needed 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Adding change Change 0x7ff518312c10 205360,1 to queue ChangeQueue check: openstack-dev/sandbox 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Event TriggerEvent patchset-created openstack-dev/sandbox master 205360,1 for change Change 0x7ff518312c10 205360,1 matched EventFilter types: patchset-created in pipeline IndependentPipelineManager silent 2015-07-25 11:42:09,258 INFO zuul.Scheduler: Adding openstack-dev/sandbox, Change 0x7ff518312c10 205360,1 to Pipeline silent 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Considering adding change Change 0x7ff518312c10 205360,1 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Unable to find change queue for change Change 0x7ff518312c10 205360,1 in project openstack-dev/sandbox 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Starting queue processor: check 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Checking for changes needed by Change 0x7ff518312c10 205360,1: 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: No changes needed 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Preparing ref for: Change 0x7ff518312c10 205360,1 2015-07-25 11:42:09,307 INFO zuul.IndependentPipelineManager: Change Change 0x7ff518312c10 205360,1 depends on changes [] 2015-07-25 11:42:09,307 DEBUG zuul.MergeClient: Submitting job gear.Job 0x7ff518325490 handle: None name: merger:merge
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine. I checked my configuration, and made sure these things: 1. I have only a master node, no slave node. 2. I have 20 idle executors on master node. 3. My master node is online. 4. My master node is set to Utilize this node as much as possible. 5. zuul is able to be notified by Gerrit, and tell Jenkins to start jobs. But the jobs are always pending. I'm now trying to setup a slave node and try again. :) And anyone has any idea of this, please let me know. Thanks. -Original Message- From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Thursday, July 23, 2015 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi, all The Jenkins jobs submitted by zuul are always pending-Waiting for next available executor . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev . __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
queue processor: patch (changed: False) 2015-07-25 11:42:09,309 DEBUG zuul.Scheduler: Run handler sleeping Thanks. :) Thanks. I'm now trying to setup a slave node and try again. :) And anyone has any idea of this, please let me know. Thanks. -Original Message- From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Thursday, July 23, 2015 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi, all The Jenkins jobs submitted by zuul are always pending-Waiting for next available executor . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev . __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev . __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev . __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
On 07/24/2015 10:08 AM, Tang Chen wrote: On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine. I checked my configuration, and made sure these things: 1. I have only a master node, no slave node. 2. I have 20 idle executors on master node. 3. My master node is online. 4. My master node is set to Utilize this node as much as possible. 5. zuul is able to be notified by Gerrit, and tell Jenkins to start jobs. But the jobs are always pending. And my Gearman reports this error sometimes. 2015-07-25 10:50:44,914 ERROR gear.Server: Exception in poll loop: Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/gear/__init__.py, line 2614, in _doPollLoop self._pollLoop() File /usr/local/lib/python2.7/dist-packages/gear/__init__.py, line 2626, in _pollLoop ret = self.poll.poll() IOError: [Errno 4] Interrupted system call Not sure if it has anything to do with this problem. In Jenkins GUI, Gearman connection is tested successfully on 127.0.0.1:4730. Thanks. I'm now trying to setup a slave node and try again. :) And anyone has any idea of this, please let me know. Thanks. -Original Message- From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Thursday, July 23, 2015 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi, all The Jenkins jobs submitted by zuul are always pending-Waiting for next available executor . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine. -Original Message- From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Thursday, July 23, 2015 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi, all The Jenkins jobs submitted by zuul are always pending-Waiting for next available executor . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi, all The Jenkins jobs submitted by zuul are always pending—Waiting for next available executor . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
On 07/22/2015 12:49 PM, Tang Chen wrote: Hi all, When I send a patch to gerrit, my zuul is notified, but jenkins jobs are not run. My CI always reports the following error: Merge Failed. This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I think, because the patch cannot be merged, the jobs are not run. Referring tohttps://www.mediawiki.org/wiki/Gerrit/Advanced_usage,I did update my master branch and make sure it is up-to-date. But it doesn't work.And other CIs from other companies didn't report this error. process_event_queue() |-- pipeline.manager.addChange() |-- report Unable to find change queue for change Change 0x7fa7ef8b6250 204446,1 in project openstack-dev/sandbox 204446 is my patch number. Anyone knows why is that ? Thanks. And also, when zuul tries to get the patch from gerrit, it executes: gerrit query --format json --all-approvals --comments --commit-message --current-patch-set --dependencies --files --patch-sets --submit-records 204337 When I try to execute it myself, it reports:Permission denied (publickey). I updated my ssh key, and uploaded the new public key to gerrit, but it doesn't work. Does anyone have any idea what's going on here ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi Tang, Reboot your master vm and then try the same. Also after restarting check the status of zuul and zuul-merger. On Wed, Jul 22, 2015 at 12:14 PM, Tang Chen tangc...@cn.fujitsu.com wrote: On 07/22/2015 12:49 PM, Tang Chen wrote: Hi all, When I send a patch to gerrit, my zuul is notified, but jenkins jobs are not run. My CI always reports the following error: Merge Failed. This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I think, because the patch cannot be merged, the jobs are not run.Referring to https://www.mediawiki.org/wiki/Gerrit/Advanced_usage, I did update my master branch and make sure it is up-to-date. But it doesn't work. And other CIs from other companies didn't report this error. process_event_queue() |-- pipeline.manager.addChange() |-- report Unable to find change queue for change Change 0x7fa7ef8b6250 204446,1 in project openstack-dev/sandbox 204446 is my patch number. Anyone knows why is that ? Thanks. And also, when zuul tries to get the patch from gerrit, it executes: gerrit query --format json --all-approvals --comments --commit-message --current-patch-set --dependencies --files --patch-sets --submit-records 204337 When I try to execute it myself, it reports:Permission denied (publickey). I updated my ssh key, and uploaded the new public key to gerrit, but it doesn't work. Does anyone have any idea what's going on here ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- *Thanks Regards,* *Abhishek* *Cloudbyte Inc. http://www.cloudbyte.com* __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
The gate is under heavy load at the moment. Maybe in a day or two it will get back to usual… From: Tang Chen tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com Reply-To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Wednesday, July 22, 2015 at 11:57 AM To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi Abhishek, On 07/22/2015 03:56 PM, Abhishek Shrivastava wrote: Hi Tang, Reboot your master vm and then try the same. Also after restarting check the status of zuul and zuul-merger. I found the problem. zuul could not fetch repo because of the proxy.. And as a result, merge failed. So the job was not run. Now it is OK. :) Thanks. :) On Wed, Jul 22, 2015 at 12:14 PM, Tang Chen tangc...@cn.fujitsu.commailto:tangc...@cn.fujitsu.com wrote: On 07/22/2015 12:49 PM, Tang Chen wrote: Hi all, When I send a patch to gerrit, my zuul is notified, but jenkins jobs are not run. My CI always reports the following error: Merge Failed.This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I think, because the patch cannot be merged, the jobs are not run. Referring to https://www.mediawiki.org/wiki/Gerrit/Advanced_usagehttps://urldefense.proofpoint.com/v2/url?u=https-3A__www.mediawiki.org_wiki_Gerrit_Advanced-5Fusaged=BQMCAwc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNcm=xPjZxaKbI6A4_QChVH5yd1mZH5dpUhZpBpBgzv53YxEs=uPutfRk7Ex5dkTVYP7ZbGR11euc8pSs1G0txZICkGWMe=, I did update my master branch and make sure it is up-to-date. But it doesn't work. And other CIs from other companies didn't report this error. process_event_queue() |-- pipeline.manager.addChange() |-- report Unable to find change queue for change Change 0x7fa7ef8b6250 204446,1 in project openstack-dev/sandbox 204446 is my patch number. Anyone knows why is that ? Thanks. And also, when zuul tries to get the patch from gerrit, it executes: gerrit query --format json --all-approvals --comments --commit-message --current-patch-set --dependencies --files --patch-sets --submit-records 204337 When I try to execute it myself, it reports:Permission denied (publickey). I updated my ssh key, and uploaded the new public key to gerrit, but it doesn't work. Does anyone have any idea what's going on here ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- [https://docs.google.com/uc?export=downloadid=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ] Thanks Regards, Abhishek Cloudbyte Inc.https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cloudbyte.comd=BQMCAwc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNcm=xPjZxaKbI6A4_QChVH5yd1mZH5dpUhZpBpBgzv53YxEs=KOIy9LLJBcxT-zC6XENVPpTuvQS7kAtxH169pLrA-sMe= __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi Abhishek, On 07/22/2015 03:56 PM, Abhishek Shrivastava wrote: Hi Tang, Reboot your master vm and then try the same. Also after restarting check the status of zuul and zuul-merger. I found the problem. zuul could not fetch repo because of the proxy.. And as a result, merge failed. So the job was not run. Now it is OK. :) Thanks. :) On Wed, Jul 22, 2015 at 12:14 PM, Tang Chen tangc...@cn.fujitsu.com mailto:tangc...@cn.fujitsu.com wrote: On 07/22/2015 12:49 PM, Tang Chen wrote: Hi all, When I send a patch to gerrit, my zuul is notified, but jenkins jobs are not run. My CI always reports the following error: Merge Failed. This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I think, because the patch cannot be merged, the jobs are not run. Referring tohttps://www.mediawiki.org/wiki/Gerrit/Advanced_usage,I did update my master branch and make sure it is up-to-date. But it doesn't work.And other CIs from other companies didn't report this error. process_event_queue() |-- pipeline.manager.addChange() |-- report Unable to find change queue for change Change 0x7fa7ef8b6250 204446,1 in project openstack-dev/sandbox 204446 is my patch number. Anyone knows why is that ? Thanks. And also, when zuul tries to get the patch from gerrit, it executes: gerrit query --format json --all-approvals --comments --commit-message --current-patch-set --dependencies --files --patch-sets --submit-records 204337 When I try to execute it myself, it reports:Permission denied (publickey). I updated my ssh key, and uploaded the new public key to gerrit, but it doesn't work. Does anyone have any idea what's going on here ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- * * *Thanks Regards, * *Abhishek* /_Cloudbyte Inc. http://www.cloudbyte.com_/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.
Hi all, When I send a patch to gerrit, my zuul is notified, but jenkins jobs are not run. My CI always reports the following error: Merge Failed. This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I think, because the patch cannot be merged, the jobs are not run. Referring to https://www.mediawiki.org/wiki/Gerrit/Advanced_usage,I did update my master branch and make sure it is up-to-date. But it doesn't work.And other CIs from other companies didn't report this error. And also, when zuul tries to get the patch from gerrit, it executes: gerrit query --format json --all-approvals --comments --commit-message --current-patch-set --dependencies --files --patch-sets --submit-records 204337 When I try to execute it myself, it reports:Permission denied (publickey). I updated my ssh key, and uploaded the new public key to gerrit, but it doesn't work. Does anyone have any idea what's going on here ? Thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
