On Sat, 13 Feb 2016 00:26:25 +0900
fumihiko kakuma wrote:
>
> On Tue, 9 Feb 2016 08:32:43 +0100
> Andreas Jaeger wrote:
>
> > On 02/09/2016 02:22 AM, fumihiko kakuma wrote:
> > > On Tue, 09 Feb 2016 09:11:22 +0900
> > > fumihiko kakuma wrote:
> > >
> > >> On Mon, 8 Feb 2016 14:20:45 -0500
>
On Tue, 9 Feb 2016 08:32:43 +0100
Andreas Jaeger wrote:
> On 02/09/2016 02:22 AM, fumihiko kakuma wrote:
> > On Tue, 09 Feb 2016 09:11:22 +0900
> > fumihiko kakuma wrote:
> >
> >> On Mon, 8 Feb 2016 14:20:45 -0500
> >> Matthew Treinish wrote:
> >>
> >>> There is nothing wrong with openstack-he
On Tue, 9 Feb 2016 08:32:43 +0100
Andreas Jaeger wrote:
> On 02/09/2016 02:22 AM, fumihiko kakuma wrote:
> > On Tue, 09 Feb 2016 09:11:22 +0900
> > fumihiko kakuma wrote:
> >
> >> On Mon, 8 Feb 2016 14:20:45 -0500
> >> Matthew Treinish wrote:
> >>
> >>> There is nothing wrong with openstack-he
On 02/09/2016 02:22 AM, fumihiko kakuma wrote:
On Tue, 09 Feb 2016 09:11:22 +0900
fumihiko kakuma wrote:
On Mon, 8 Feb 2016 14:20:45 -0500
Matthew Treinish wrote:
There is nothing wrong with openstack-health it's behaving as currently
expected. There is a known limitation with the dashboard
On Tue, 09 Feb 2016 09:11:22 +0900
fumihiko kakuma wrote:
> On Mon, 8 Feb 2016 14:20:45 -0500
> Matthew Treinish wrote:
>
> > There is nothing wrong with openstack-health it's behaving as currently
> > expected. There is a known limitation with the dashboard right now where
> > results aren't c
On Mon, 8 Feb 2016 19:23:16 +
Jeremy Stanley wrote:
> On 2016-02-08 08:13:38 +0900 (+0900), fumihiko kakuma wrote:
> [...]
> > BTW can you also explain the non-indication of periodic pipeline data
> > by openstack-helth and tell the resolution to it?
>
> At least some periodic jobs do seem t
On Mon, 8 Feb 2016 14:20:45 -0500
Matthew Treinish wrote:
> On Mon, Feb 08, 2016 at 08:13:38AM +0900, fumihiko kakuma wrote:
> > Hi Jeremy,
> >
> > On Fri, 5 Feb 2016 14:45:17 +
> > Jeremy Stanley wrote:
> >
> > > On 2016-02-05 09:00:24 +0100 (+0100), Andreas Jaeger wrote:
> > > > One idea
On 2016-02-08 08:13:38 +0900 (+0900), fumihiko kakuma wrote:
[...]
> BTW can you also explain the non-indication of periodic pipeline data
> by openstack-helth and tell the resolution to it?
At least some periodic jobs do seem to be indexed by it, for example
the ones run against openstack-tempest
On Mon, Feb 08, 2016 at 08:13:38AM +0900, fumihiko kakuma wrote:
> Hi Jeremy,
>
> On Fri, 5 Feb 2016 14:45:17 +
> Jeremy Stanley wrote:
>
> > On 2016-02-05 09:00:24 +0100 (+0100), Andreas Jaeger wrote:
> > > One idea: Remove the branch filters you created.
> > [...]
> >
> > Correct. From Zu
Hi Jeremy,
On Fri, 5 Feb 2016 14:45:17 +
Jeremy Stanley wrote:
> On 2016-02-05 09:00:24 +0100 (+0100), Andreas Jaeger wrote:
> > One idea: Remove the branch filters you created.
> [...]
>
> Correct. From Zuul's perspective periodic jobs are triggered simply
> by a changeless/refless timer,
On 2016-02-05 09:00:24 +0100 (+0100), Andreas Jaeger wrote:
> One idea: Remove the branch filters you created.
[...]
Correct. From Zuul's perspective periodic jobs are triggered simply
by a changeless/refless timer, and thus branchless since there's no
associated Gerrit change or Git ref from whic
Hi Andreas,
Thank you for your help very much.
I seem to make many mistakes.
I believe that they were just recovered.
Best regards,
Fumihiko Kakuma
On Fri, 5 Feb 2016 09:00:24 +0100
Andreas Jaeger wrote:
> On 02/04/2016 02:47 PM, fumihiko kakuma wrote:
> > Hi infra team,
> >
> > My merged chan
On 02/04/2016 02:47 PM, fumihiko kakuma wrote:
Hi infra team,
My merged changes added the periodic-neutron queue and jobs to
be run on it the other day[1]. But the periodic-neutron queue seems
to have some problems.
The periodic-neutron does not work for ovs-native jobs.
I think that periodic-t
13 matches
Mail list logo
