On 07/24/2018 05:48 AM, Michal Privoznik wrote:
> On 07/23/2018 03:10 PM, John Ferlan wrote:
>>
>>
>> On 07/23/2018 04:01 AM, Michal Prívozník wrote:
>>> On 07/17/2018 09:15 PM, John Ferlan wrote:
On 07/04/2018 05:23 AM, Michal Privoznik wrote:
> Extend this existing test so th
On 07/23/2018 03:10 PM, John Ferlan wrote:
>
>
> On 07/23/2018 04:01 AM, Michal Prívozník wrote:
>> On 07/17/2018 09:15 PM, John Ferlan wrote:
>>>
>>>
>>> On 07/04/2018 05:23 AM, Michal Privoznik wrote:
Extend this existing test so that a case when IQN is provided is
tested too. Since a
On 07/23/2018 04:01 AM, Michal Prívozník wrote:
> On 07/17/2018 09:15 PM, John Ferlan wrote:
>>
>>
>> On 07/04/2018 05:23 AM, Michal Privoznik wrote:
>>> Extend this existing test so that a case when IQN is provided is
>>> tested too. Since a special iSCSI interface is created and its
>>> name is
On 07/17/2018 09:15 PM, John Ferlan wrote:
>
>
> On 07/04/2018 05:23 AM, Michal Privoznik wrote:
>> Extend this existing test so that a case when IQN is provided is
>> tested too. Since a special iSCSI interface is created and its
>> name is randomly generated at runtime we need to link with
>> v
On 07/04/2018 05:23 AM, Michal Privoznik wrote:
> Extend this existing test so that a case when IQN is provided is
> tested too. Since a special iSCSI interface is created and its
> name is randomly generated at runtime we need to link with
> virrandommock to have predictable names.
>
> Signed-
Extend this existing test so that a case when IQN is provided is
tested too. Since a special iSCSI interface is created and its
name is randomly generated at runtime we need to link with
virrandommock to have predictable names.
Signed-off-by: Michal Privoznik
---
tests/viriscsitest.c | 75 ++
