From: Daniel P. Berrangé <berra...@redhat.com>
We're not using avocado anymore, so while the TODO item is still
relevant, suggesting use of avocado.utils is not.
Reviewed-by: Alex Bennée <alex.ben...@linaro.org>
Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>
Message-Id: <20241121154218.1423005-5-berra...@redhat.com>
Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
---
tests/functional/test_m68k_nextcube.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tests/functional/test_m68k_nextcube.py
b/tests/functional/test_m68k_nextcube.py
index 89385a134a..0124622c40 100755
--- a/tests/functional/test_m68k_nextcube.py
+++ b/tests/functional/test_m68k_nextcube.py
@@ -37,8 +37,7 @@ def check_bootrom_framebuffer(self, screenshot_path):
self.vm.launch()
self.log.info('VM launched, waiting for display')
- # TODO: Use avocado.utils.wait.wait_for to catch the
- # 'displaysurface_create 1120x832' trace-event.
+ # TODO: wait for the 'displaysurface_create 1120x832' trace-event.
time.sleep(2)
self.vm.cmd('human-monitor-command',
--
2.39.5
