qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/1] hw/arm/aspeed: Add fby35 machine type


From: Cédric Le Goater
Subject: Re: [PATCH 0/1] hw/arm/aspeed: Add fby35 machine type
Date: Tue, 3 May 2022 23:35:09 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0

On 5/3/22 22:44, Peter Delevoryas wrote:
Hey everyone,

I'm submitting another Facebook (Meta Platforms) machine type: this time I'm
including an acceptance test too.

Unfortunately, this machine boots _very_ slowly. 300+ seconds.

This is too much for avocado tests.

I'm not sure why this is (so I don't know how to fix it easily)

The fuji has the same kind of problem. It takes ages to load the lzma ramdisk.
Could it be a modeling issue ? or how the FW image is compiled ?

Thanks,

C.


and I don't know how to override
the avocado test timeout just for a single test, so I increased the global
timeout for all "boot_linux_console.py" tests from 90s to 400s. I doubt this is
acceptable, but what other option is there? Should I add
AVOCADO_TIMEOUT_EXPECTED?

@skipUnless(os.getenv('AVOCADO_TIMEOUT_EXPECTED'), 'Test might timeout')

What is the point of this environment variable though, except to skip it in CIT?
If I run the test with this environment variable defined, it doesn't disable the
timeout, it just skips it right? I want an option to run this test with a larger
timeout.

Thanks,
Peter

Peter Delevoryas (1):
   hw/arm/aspeed: Add fby35 machine type

  hw/arm/aspeed.c                     | 63 +++++++++++++++++++++++++++++
  tests/avocado/boot_linux_console.py | 20 ++++++++-
  2 files changed, 82 insertions(+), 1 deletion(-)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]