On Tue, Apr 2, 2019 at 3:30 PM Michal Privoznik wrote:
>
> On 4/2/19 10:45 AM, Christian Ehrhardt wrote:
> > On Mon, Apr 1, 2019 at 4:35 PM Michal Privoznik wrote:
> >>
> >> On 4/1/19 4:25 PM, Christian Ehrhardt wrote:
> >>> Hi,
> >>> I happened to analyze a bug [1] report I got from a friend and
On 4/2/19 10:45 AM, Christian Ehrhardt wrote:
> On Mon, Apr 1, 2019 at 4:35 PM Michal Privoznik wrote:
>>
>> On 4/1/19 4:25 PM, Christian Ehrhardt wrote:
>>> Hi,
>>> I happened to analyze a bug [1] report I got from a friend and for
>>> quite a while it was rather elusive. But I now finally got it
On Mon, Apr 1, 2019 at 4:35 PM Michal Privoznik wrote:
>
> On 4/1/19 4:25 PM, Christian Ehrhardt wrote:
> > Hi,
> > I happened to analyze a bug [1] report I got from a friend and for
> > quite a while it was rather elusive. But I now finally got it
> > reproducible [2] enough to share it with the
On 4/1/19 4:25 PM, Christian Ehrhardt wrote:
Hi,
I happened to analyze a bug [1] report I got from a friend and for
quite a while it was rather elusive. But I now finally got it
reproducible [2] enough to share it with the community.
The TL;DR of what I see is:
- an automation with python-libvir
Hi,
I happened to analyze a bug [1] report I got from a friend and for
quite a while it was rather elusive. But I now finally got it
reproducible [2] enough to share it with the community.
The TL;DR of what I see is:
- an automation with python-libvirt gets a SIGINT
- cleanup runs destroy and furt
