@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
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
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
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
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
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
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
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
(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
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
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
]
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
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
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
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
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
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.
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.
18 matches
Mail list logo
