Hello All.
We checked this with did and postgres connection error is not an error
(although it prints stacktrace... cannot we not print stacktraces, please,
for antyhing that we handle in code... it is really confusing when you need
to find the root cause).
The test is checking for dwhd to be up
Hello All.
With Shirly help we found that 4.1 was using master and when ovirt_engine_dwh
was branched today 4.1 job was not updated. This resulted in 4.1 repo be
poisoned with 4.1 dwh rpm. I manually cleared it and waiting for test
results, looks like we have a pile up on Jenkins due to lot of pat
I fixed the master bug. Is dwh in master still failing?
Best regards,
Shirly Radco
BI Software Engineer
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
On Tue, Jan 17, 2017 at 5:30 PM, Anton Marchukov
wrote:
> Hello All.
>
> With Shirly help we found that
Hello Shirly.
Thanks for your fix. No. Today there are no things of dwh related failures
in both master and 4.1
Anton.
On Tue, Jan 17, 2017 at 9:26 PM, Shirly Radco wrote:
> I fixed the master bug. Is dwh in master still failing?
>
> Best regards,
>
> Shirly Radco
>
> BI Software Engineer
> Re
On Wed, Jan 18, 2017 at 3:09 PM, Anton Marchukov
wrote:
> Hello Shirly.
>
> Thanks for your fix. No. Today there are no things of dwh related failures
> in both master and 4.1
>
Would be great if it could be published, so us mere mortals could enjoy the
fix and run o-s-t as well :-)
Y.
>
> Ant
On Wed, Jan 18, 2017 at 10:59 PM, Yaniv Kaul wrote:
>
>
> On Wed, Jan 18, 2017 at 3:09 PM, Anton Marchukov
> wrote:
>
>> Hello Shirly.
>>
>> Thanks for your fix. No. Today there are no things of dwh related
>> failures in both master and 4.1
>>
>
> Would be great if it could be published, so us
