Re: [libvirt] [PATCH 3/5] tests: don't use unix socket path that matches auto-generated path

On Wed, Aug 30, 2017 at 03:38:12PM +0200, Michal Privoznik wrote: > On 08/30/2017 02:45 PM, Pavel Hrdina wrote: > > On Wed, Aug 30, 2017 at 02:33:00PM +0200, Michal Privoznik wrote: > >> On 08/30/2017 01:40 PM, Pavel Hrdina wrote: > >>> The test was introduced by 60135b22db6d. > >>> > >>> The

Re: [libvirt] [PATCH 3/5] tests: don't use unix socket path that matches auto-generated path

On 08/30/2017 02:45 PM, Pavel Hrdina wrote: > On Wed, Aug 30, 2017 at 02:33:00PM +0200, Michal Privoznik wrote: >> On 08/30/2017 01:40 PM, Pavel Hrdina wrote: >>> The test was introduced by 60135b22db6d. >>> >>> The auto-generated path is removed by post-parse callback which >>> also changes the

Re: [libvirt] [PATCH 3/5] tests: don't use unix socket path that matches auto-generated path

On Wed, Aug 30, 2017 at 02:33:00PM +0200, Michal Privoznik wrote: > On 08/30/2017 01:40 PM, Pavel Hrdina wrote: > > The test was introduced by 60135b22db6d. > > > > The auto-generated path is removed by post-parse callback which > > also changes the mode from "connect" to "bind" since the

Re: [libvirt] [PATCH 3/5] tests: don't use unix socket path that matches auto-generated path

On 08/30/2017 01:40 PM, Pavel Hrdina wrote: > The test was introduced by 60135b22db6d. > > The auto-generated path is removed by post-parse callback which > also changes the mode from "connect" to "bind" since the auto-generated > path makes sense only for "bind" mode. > > Signed-off-by: Pavel

[libvirt] [PATCH 3/5] tests: don't use unix socket path that matches auto-generated path

The test was introduced by 60135b22db6d. The auto-generated path is removed by post-parse callback which also changes the mode from "connect" to "bind" since the auto-generated path makes sense only for "bind" mode. Signed-off-by: Pavel Hrdina ---