On Mon, Apr 11, 2016 at 1:56 PM, Clark Boylan wrote:
> On Mon, Apr 11, 2016, at 10:52 AM, Jakub Libosvar wrote:
>> On 04/11/2016 06:41 PM, Clark Boylan wrote:
>> > On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote:
>> >> Hi,
>> >>
>> >> recently we hit an issue in
On 04/11/2016 06:41 PM, Clark Boylan wrote:
> On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote:
>> Hi,
>>
>> recently we hit an issue in Neutron with tests getting stuck [1]. As a
>> side effect we discovered logs are not collected properly which makes it
>> hard to find the root cause. The
On Mon, Apr 11, 2016, at 10:52 AM, Jakub Libosvar wrote:
> On 04/11/2016 06:41 PM, Clark Boylan wrote:
> > On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote:
> >> Hi,
> >>
> >> recently we hit an issue in Neutron with tests getting stuck [1]. As a
> >> side effect we discovered logs are not
On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote:
> Hi,
>
> recently we hit an issue in Neutron with tests getting stuck [1]. As a
> side effect we discovered logs are not collected properly which makes it
> hard to find the root cause. The reason of missing logs is that we send
> SIGKILL
On Mon, Apr 11, 2016 at 9:39 AM, Morales, Victor
wrote:
>
>
>
>
>
> On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote:
>
>>Hi,
>>
>>recently we hit an issue in Neutron with tests getting stuck [1]. As a
>>side effect we discovered logs are not collected
On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote:
>Hi,
>
>recently we hit an issue in Neutron with tests getting stuck [1]. As a
>side effect we discovered logs are not collected properly which makes it
>hard to find the root cause. The reason of missing logs is that we send
Hi,
recently we hit an issue in Neutron with tests getting stuck [1]. As a
side effect we discovered logs are not collected properly which makes it
hard to find the root cause. The reason of missing logs is that we send
SIGKILL to whatever gate hook is running when we hit the global timeout
per