### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Sun Nov 15 03:41:15 2015
Date Range Processed: yesterday
( 2015-Nov-14 )
Period is day.
Detail Level of Output: 0
joining the rant. This is not the first time we experience that.
On Sun, Nov 15, 2015 at 3:11 PM, Eyal Edri wrote:
> there seems to be a queue now in progress, so that's the reason it takes
> time.
> also, we're investigating an issue with the proxy from phx DC, that is
> down
thanks for reporting roy, do you have an example for a patch that is
waiting?
the more reports we'll get on issues with the infra, the more chance there
will be to fix it,
we don't monitor the per patch jobs, its not possible with the amount, so
we rely on reports from developers in order to fix
I post to infra usually. I will report on thread when I see more of these.
But why rely on developers report? Can't we measure how much time a job
takes to trigger and if
it exceeds it, report to infra automatically.
On Sun, Nov 15, 2015 at 5:55 PM, Eyal Edri wrote:
> thanks
Hi infra,
I've observed over the weekend and today that sometimes ovirt-engine's CI
seems to be stuck.
E.g., take a look at [1]. The first out of four jobs started about 90
mintues(!) ago, and nothing seems to have progressed since.
Can someone please take a look?
Thanks,
Allon
[1]
there seems to be a queue now in progress, so that's the reason it takes
time.
also, we're investigating an issue with the proxy from phx DC, that is down
and affecting the jobs.
but regadless, i wonder if we can't enable concurrent jobs for