[Starlingx-discuss] POST_FAILURE >> RE: [Release] stx.2018.10 status & next steps
There appears to be multiple examples of this zuul POST_FAILURE: https://review.openstack.org/#/c/605236/ https://review.openstack.org/#/c/605285/ Ghada -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Wednesday, September 26, 2018 9:20 PM To: Penney, Don Cc: Jones, Bruce E; Khalil, Ghada; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [Release] stx.2018.10 status & next steps On Wed, Sep 26, 2018 at 7:55 PM, Penney, Don <Don.Penney@windriver.com> wrote:
One of these open reviews is blocked by a Zuul failure, in the new openstack-tox-docs job, which would be unrelated to the updated https://review.openstack.org/#/c/605462/
[...]
I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now.
A POST_FAILURE on a job is almost always a failure in the infrastructure of some sort. Whether a recheck is going to be useful depends on what it is. This one does appear to be a job configuration failure, but the cause is not immediately obvious to me... dt -- Dean Troyer dtroyer@gmail.com
On Wed, Sep 26, 2018 at 10:08 PM, Khalil, Ghada <Ghada.Khalil@windriver.com> wrote:
There appears to be multiple examples of this zuul POST_FAILURE: https://review.openstack.org/#/c/605236/ https://review.openstack.org/#/c/605285/
so the actual failure here (all three of these so far) is the tox 'docs' environment is not present in these reviews. Which is normal, what is not is why the docs job is running here when it is not present in .zuul.yaml. These are both present in master so I've rebased all three of these on master and hopefully it will clear. In the morning I'll dig in to why that job is running when it isn't called (could be due to inheriting from OpenStack default jobs)... dt -- Dean Troyer dtroyer@gmail.com
participants (2)
-
Dean Troyer
-
Khalil, Ghada