On 7/29/24 8:02 AM, Philippe Mathieu-Daudé wrote:
Does that restore feature parity for macOS developers? Because this
community has been left behind ignored for over 2 years and already
looked at alternatives for functional testing.
Hi Phillipe,
As early as Avocado 102.0, macOS support is pretty complete. The exact
words on the release notes[1] are:
"User of macOS will have a better experience when using Avocado. The
full set of Avocado’s selftests are now run under macOS on CI. Please be
advised that macOS is not currently supported at the same level of
Linux-based operating systems due to the lack of
contributors/maintainers with access to the needed hardware. If you are
a user/developer and are willing to contribute to this, please let the
Avocado team know."
When it comes to the lack of updates, that is a longer discussion
indeed. When it comes to alternatives, I don't expect the QEMU project
to do anything else than what it's in its best interest. As late as this
can be, please take it for what it's worth. If it does any good to
QEMU, please consider it.
Best,
- Cleber.
[1] - https://avocado-framework.readthedocs.io/en/latest/releases/102_0.html
Reference:
https://avocado-framework.readthedocs.io/en/103.0/releases/lts/103_0.html
Signed-off-by: Cleber Rosa <cr...@redhat.com>
---
pythondeps.toml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pythondeps.toml b/pythondeps.toml
index f6e590fdd8..175cf99241 100644
--- a/pythondeps.toml
+++ b/pythondeps.toml
@@ -30,5 +30,5 @@ sphinx_rtd_theme = { accepted = ">=0.5", installed
= "1.1.1" }
# Note that qemu.git/python/ is always implicitly installed.
# Prefer an LTS version when updating the accepted versions of
# avocado-framework, for example right now the limit is 92.x.
-avocado-framework = { accepted = "(>=88.1, <93.0)", installed =
"88.1", canary = "avocado" }
+avocado-framework = { accepted = "(>=103.0, <104.0)", installed =
"103.0", canary = "avocado" }
pycdlib = { accepted = ">=1.11.0" }