Hi, I was looking at Thomas' last series [*] where he adds the NeXTcube machine, thinking about enforcing a new rule "new machines must have tests". Then I realized the UART is not yet implemented, so our current sample tests are not helpful.
Since the framebuffer is working, I gave a try at dumping the screen content via the HMP 'screendump' command, then parsing the screenshot with an OCR tool. The default ROM dump the bootlog to a console. Using the old good tesseract tool we can recover some useful words to be sure the guest is sane, its framebuffer is definitively working. This test takes less than 6s on Travis-CI: https://travis-ci.org/philmd/qemu/builds/552174983#L1836 AVOCADO tests/acceptance (3/9) /home/travis/build/philmd/qemu/tests/acceptance/machine_m68k_nextcube.py:NextCubeMachine.test_bootrom_framebuffer: PASS (5.69 s) Regards, Phil. Based-on: 20190628181536.13729-1-h...@tuxfamily.org [*] "m68k: Add basic support for the NeXTcube machine" https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg06393.html Philippe Mathieu-Daudé (2): tests/acceptance: Add test of NeXTcube framebuffer using OCR .travis.yml: Let the avocado job run the NeXTcube tests .travis.yml | 5 ++- tests/acceptance/machine_m68k_nextcube.py | 50 +++++++++++++++++++++++ 2 files changed, 54 insertions(+), 1 deletion(-) create mode 100644 tests/acceptance/machine_m68k_nextcube.py -- 2.19.1
