Re: [openstack-dev] [all] Zuul Error for commits

[Jeremy Stanley]

On 2017-10-05 06:36:10 -0600 (-0600), Boden Russell wrote:
> [1] Based on [1] I though Zuul v3 jobs were non-voting at this
> point in time and so a v3 job failure wouldn't -1V stalling a
> patch.
> 
> However, I'm also noticing that v3 jobs are failing patches in
> neutron-lib ([2] for ex).
> 
> What am I missing here??
[...]

Matt misused the term "non-voting" in that message to which Clark
was replying. Zuul v3 is certainly "voting" on changes in the check
pipeline in the way that other third-party CI systems do, so that
we/you have an opportunity to fix any broken v3 jobs before we roll
forward onto v3 again (hopefully very, very soon now).

It is however non-gating, in the sense that it will not attempt to
merge a change nor prevent it from merging. The "Zuul" account is
only leaving advisory -1 and +1 verify votes on changes and leaving
authoritative control over testing/merging to the "Jenkins" account.
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
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] [all] Zuul Error for commits

[Andreas Jaeger]

On 2017-10-05 13:43, Goutham Pratapa wrote:
> Hi all,
> 
> 
> I have made a commit to a Kingbird-project and Zuul jobs ran and a job
> namely openstack-tox-py27
> 
> 
> failed with the error *TIMED_OUT in 2h 32m 23s *which resulted in -1 how
> can I retrigger it is
> 
> this a known issue??
> 
> Commit for reference: https://review.openstack.org/#/c/487813/
> 
> Any help?

http://zuulv3.openstack.org shows that 487813 is still getting
processed, Zuul v3 has a much smaller number of nodes. So, your recheck
worked.

The -1 by Zuul v3 does not block you merging a change, you can go ahead
and merge it. If you have touched zuul v3 files, I would wait for it,
otherwise review the jobs and decide whether you need to wait or want to
ignore the timeout. There's no technical limitation to block the merge,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [all] Zuul Error for commits

[Boden Russell]

On 10/5/17 5:43 AM, Goutham Pratapa wrote:
> failed with the error *TIMED_OUT in 2h 32m 23s *which resulted in -1 how
> can I retrigger it is
>

[1] Based on [1] I though Zuul v3 jobs were non-voting at this point in time and
so a v3 job failure wouldn't -1V stalling a patch.

However, I'm also noticing that v3 jobs are failing patches in neutron-lib
([2] for ex).

What am I missing here??

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-October/123052.html
[2] https://review.openstack.org/#/c/502698/

__
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] [all] Zuul Error for commits

[Goutham Pratapa]

Hi,

It triggers only Jenkins job but not ZUUL jobs

Thanks
Goutham

On Thu, 5 Oct 2017 at 5:26 PM, Kekane, Abhishek 
wrote:

> Goutham,
>
>
>
> Add ‘recheck’ as a comment. It will retrigger the jenkins jobs.
>
>
>
> Thank you,
>
>
>
> Abhishek
>
>
>
> *From:* Goutham Pratapa [mailto:pratapagout...@gmail.com]
> *Sent:* Thursday, October 05, 2017 5:14 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [all] Zuul Error for commits
>
>
>
> Hi all,
>
> I have made a commit to a Kingbird-project and Zuul jobs ran and a job
> namely openstack-tox-py27
> 
>
>
>
> failed with the error *TIMED_OUT** in 2h 32m 23s *which resulted in -1
> how can I retrigger it is
>
>
>
> this a known issue??
>
>
>
> Commit for reference: https://review.openstack.org/#/c/487813/
>
>
>
> Any help?
>
>
>
> Thanks in advance..
>
>
>
> Cheers !!!
>
> Goutham Pratapa
>
> __
> Disclaimer: This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding.
> __
> 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
>
-- 
Cheers !!!
Goutham Pratapa
__
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] [all] Zuul Error for commits

[Kekane, Abhishek]

Goutham,

Add ‘recheck’ as a comment. It will retrigger the jenkins jobs.

Thank you,

Abhishek

From: Goutham Pratapa [mailto:pratapagout...@gmail.com]
Sent: Thursday, October 05, 2017 5:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [all] Zuul Error for commits

Hi all,

I have made a commit to a Kingbird-project and Zuul jobs ran and a job namely 
openstack-tox-py27


failed with the error TIMED_OUT in 2h 32m 23s which resulted in -1 how can I 
retrigger it is

this a known issue??

Commit for reference: https://review.openstack.org/#/c/487813/

Any help?

Thanks in advance..

Cheers !!!
Goutham Pratapa

__
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
__
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