On 13.03.2023 12:15, Roger Pau Monné wrote:
> On Mon, Mar 13, 2023 at 11:43:43AM +0100, Jan Beulich wrote:
>> On 13.03.2023 11:31, Roger Pau Monné wrote:
>>> On Fri, Mar 10, 2023 at 03:32:41PM +0100, Jan Beulich wrote:
On 10.03.2023 14:38, Roger Pau Monné wrote:
> On Fri, Mar 10, 2023 at 1
On Mon, Mar 13, 2023 at 11:43:43AM +0100, Jan Beulich wrote:
> On 13.03.2023 11:31, Roger Pau Monné wrote:
> > On Fri, Mar 10, 2023 at 03:32:41PM +0100, Jan Beulich wrote:
> >> On 10.03.2023 14:38, Roger Pau Monné wrote:
> >>> On Fri, Mar 10, 2023 at 12:06:29PM +0100, Jan Beulich wrote:
> On 0
On 13.03.2023 11:31, Roger Pau Monné wrote:
> On Fri, Mar 10, 2023 at 03:32:41PM +0100, Jan Beulich wrote:
>> On 10.03.2023 14:38, Roger Pau Monné wrote:
>>> On Fri, Mar 10, 2023 at 12:06:29PM +0100, Jan Beulich wrote:
On 09.03.2023 17:58, Roger Pau Monne wrote:
> Introduce an install targ
On Fri, Mar 10, 2023 at 03:32:41PM +0100, Jan Beulich wrote:
> On 10.03.2023 14:38, Roger Pau Monné wrote:
> > On Fri, Mar 10, 2023 at 12:06:29PM +0100, Jan Beulich wrote:
> >> On 09.03.2023 17:58, Roger Pau Monne wrote:
> >>> Introduce an install target, like it's used by other tests. This
> >>>
On 10.03.2023 14:38, Roger Pau Monné wrote:
> On Fri, Mar 10, 2023 at 12:06:29PM +0100, Jan Beulich wrote:
>> On 09.03.2023 17:58, Roger Pau Monne wrote:
>>> Introduce an install target, like it's used by other tests. This
>>> allows running the test on the installed systems, which is easier than
On Fri, Mar 10, 2023 at 12:06:29PM +0100, Jan Beulich wrote:
> On 09.03.2023 17:58, Roger Pau Monne wrote:
> > Introduce an install target, like it's used by other tests. This
> > allows running the test on the installed systems, which is easier than
> > running it during the build phase when deal
On 09.03.2023 17:58, Roger Pau Monne wrote:
> Introduce an install target, like it's used by other tests. This
> allows running the test on the installed systems, which is easier than
> running it during the build phase when dealing with automated testing.
> Strictly speaking the vpci test doesn't
Introduce an install target, like it's used by other tests. This
allows running the test on the installed systems, which is easier than
running it during the build phase when dealing with automated testing.
Strictly speaking the vpci test doesn't require to be run on a Xen
host currently, but that