Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qemu: Updated test image URL as the old one is no longer available. Improved test block by checking every built binary's --version output for either the expected version string or "QEMU emulator" to verify that the binaries have been built correctly. #769

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

akemin-dayo
Copy link
Contributor

@akemin-dayo akemin-dayo commented Oct 15, 2021

Here's what the new brew test qemu output is like:

karen002ppc-osx104:~ karen$ brew test qemu
Testing qemu
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-aarch64 --version

(process:28027): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-alpha --version

(process:28029): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-arm --version

(process:28031): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-cris --version

(process:28033): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-i386 --version

(process:28035): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-lm32 --version

(process:28037): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-m68k --version

(process:28039): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-microblaze --version

(process:28041): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-microblazeel --version

(process:28043): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-mips --version

(process:28045): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-mips64 --version

(process:28047): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-mips64el --version

(process:28049): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-mipsel --version

(process:28051): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-moxie --version

(process:28053): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-or32 --version

(process:28055): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-ppc --version

(process:28057): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-ppc64 --version

(process:28059): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-ppcemb --version

(process:28061): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-s390x --version

(process:28063): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-sh4 --version

(process:28065): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-sh4eb --version

(process:28067): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-sparc --version

(process:28069): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-sparc64 --version

(process:28071): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-tricore --version

(process:28073): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-unicore32 --version

(process:28075): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-x86_64 --version

(process:28077): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-xtensa --version

(process:28079): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-system-xtensaeb --version

(process:28081): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
==> Downloading https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/FD12FLOPPY.zip
################################################################################################################################################################################################### 100.0%
==> /usr/local/Cellar/qemu/2.2.1_1/bin/qemu-img info FLOPPY.img
karen002ppc-osx104:~ karen$ brew audit qemu
karen002ppc-osx104:~ karen$ 

brew install qemuPASS (OS X 10.5.8 [--cc=gcc-7 is required for now, I'm working on a PR to address this] and OS X 10.4.11, both PowerPC)
brew audit qemuPASS
brew test qemuPASS

…mproved test block by checking every built binary's `--version` output for either the expected version string or "QEMU emulator" to verify that the binaries have been built correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant