Peter Maydell writes:
> On Fri, 3 Mar 2023 at 20:59, Fabiano Rosas wrote:
>>
>> Peter Maydell writes:
>>
>> > On Tue, 28 Feb 2023 at 19:28, Fabiano Rosas wrote:
>> >>
>> >> The migration tests are currently broken for an aarch64 host because
>> >> the tests pass no 'machine' and 'cpu' options
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On Tue, 28 Feb 2023 at 19:28, Fabiano Rosas wrote:
> >
> > The migration tests are currently broken for an aarch64 host because
> > the tests pass no 'machine' and 'cpu' options on the QEMU command
> > line.
> >
> > Add a separate class to each
On Fri, 3 Mar 2023 at 20:59, Fabiano Rosas wrote:
>
> Peter Maydell writes:
>
> > On Tue, 28 Feb 2023 at 19:28, Fabiano Rosas wrote:
> >>
> >> The migration tests are currently broken for an aarch64 host because
> >> the tests pass no 'machine' and 'cpu' options on the QEMU command
> >> line.
>
Peter Maydell writes:
> On Tue, 28 Feb 2023 at 19:28, Fabiano Rosas wrote:
>>
>> The migration tests are currently broken for an aarch64 host because
>> the tests pass no 'machine' and 'cpu' options on the QEMU command
>> line.
>>
>> Add a separate class to each architecture so that we can
On Tue, 28 Feb 2023 at 19:28, Fabiano Rosas wrote:
>
> The migration tests are currently broken for an aarch64 host because
> the tests pass no 'machine' and 'cpu' options on the QEMU command
> line.
>
> Add a separate class to each architecture so that we can specify
> 'machine' and 'cpu'
The migration tests are currently broken for an aarch64 host because
the tests pass no 'machine' and 'cpu' options on the QEMU command
line.
Add a separate class to each architecture so that we can specify
'machine' and 'cpu' options instead of relying on defaults.
Add a skip decorator to keep
