On Fri, Oct 25, 2024 at 09:47:07AM +0200, Thomas Huth wrote:
> On 21/10/2024 17.02, Thomas Huth wrote:
> > On 21/10/2024 14.36, Daniel P. Berrangé wrote:
> > > This ensures that if a functional test runs QEMU with a writable
> > > disk pointing to a cached asset, an error will be reported, rather
>
On 21/10/2024 17.02, Thomas Huth wrote:
On 21/10/2024 14.36, Daniel P. Berrangé wrote:
This ensures that if a functional test runs QEMU with a writable
disk pointing to a cached asset, an error will be reported, rather
than silently modifying the cache file.
As an example, tweaking test_sbsaref
On 21/10/24 09:36, Daniel P. Berrangé wrote:
This ensures that if a functional test runs QEMU with a writable
disk pointing to a cached asset, an error will be reported, rather
than silently modifying the cache file.
As an example, tweaking test_sbsaref.py to set snapshot=off,
results in a clear
On 21/10/2024 14.36, Daniel P. Berrangé wrote:
This ensures that if a functional test runs QEMU with a writable
disk pointing to a cached asset, an error will be reported, rather
than silently modifying the cache file.
As an example, tweaking test_sbsaref.py to set snapshot=off,
results in a cle
This ensures that if a functional test runs QEMU with a writable
disk pointing to a cached asset, an error will be reported, rather
than silently modifying the cache file.
As an example, tweaking test_sbsaref.py to set snapshot=off,
results in a clear error:
Command: ./build/qemu-system-aarch64
