diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/118/all/1317 | 79 | ||||
| -rw-r--r-- | results/classifier/118/all/1317603 | 215 |
2 files changed, 294 insertions, 0 deletions
diff --git a/results/classifier/118/all/1317 b/results/classifier/118/all/1317 new file mode 100644 index 00000000..8b4e5bcd --- /dev/null +++ b/results/classifier/118/all/1317 @@ -0,0 +1,79 @@ +graphic: 0.989 +peripherals: 0.987 +semantic: 0.982 +device: 0.977 +debug: 0.971 +socket: 0.958 +vnc: 0.955 +virtual: 0.948 +assembly: 0.947 +x86: 0.944 +risc-v: 0.944 +arm: 0.940 +user-level: 0.937 +mistranslation: 0.933 +performance: 0.930 +ppc: 0.929 +register: 0.929 +architecture: 0.926 +PID: 0.925 +permissions: 0.924 +files: 0.924 +TCG: 0.919 +hypervisor: 0.906 +boot: 0.893 +VMM: 0.893 +network: 0.884 +kernel: 0.882 +KVM: 0.864 +i386: 0.858 + +"make-check avocado" doesn't work in ubuntu 1804 because of older versions of pip and setuputils +Description of problem: +make check-avocado tests don't run in Ubuntu 18.04, I get an error: + +`Command "python setup.py egg_info" failed with error code 1 in /qemu/python/` + +It looks like pip and setuputils are too old in 18.04 (which is still an active lts version supposedly). +Steps to reproduce: +Compile qemu in Ubuntu 18.04. This is an ad-hoc example with docker but I reproduced it in Ubuntu 18.04 VM too +1. Create docker from Dockerfile [Dockerfile](/uploads/a5748cabca5319f467cbc0b803ed9104/Dockerfile): + +<code>FROM ubuntu:18.04 +RUN apt update +RUN apt-get install -y git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build git-email libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev librbd-dev librdmacm-dev libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev valgrind xfslibs-dev python3-venv</code> + +`docker build -t 1804qemuavocado .` + +2. Run shell inside of docker: + +`docker run -it 1804qemuavocado bash` + +3. Clone QEMU: + +`git clone --depth 1 https://github.com/qemu/qemu.git` + +4. Build QEMU (targets and parameters should not matter much): + +<code>cd qemu +mkdir build +cd build +../configure --target-list=x86_64-softmmu +ninja</code> + +5. Attempt to run tests: + +`make check-avocado` + +6. Get an error: + +<code>/usr/bin/python3 -B /qemu/meson/meson.py introspect --targets --tests --benchmarks | /usr/bin/python3 -B scripts/mtest2make.py > Makefile.mtest + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + VENV /qemu/build/tests/venv + VENVPIP install -e /qemu/python/ +Command "python setup.py egg_info" failed with error code 1 in /qemu/python/ +/qemu/tests/Makefile.include:115: recipe for target '/qemu/build/tests/venv' failed +make: *** [/qemu/build/tests/venv] Error 1</code> +Additional information: +As far as I understand, upgrading pip in system won't help, because venv creates an environment with base pip version (9 in case of Ubuntu 18.04). I tried creating a small patch [patch.diff](/uploads/0ae4883106773f0ea940d27b74219732/patch.diff) for tests/Makefile.include, that upgrades pip and setuputils in venv to the latest version, and it seem to help, but I don't know if it's the right solution to always have the latest version. Probably some LTS version should be chosen, if such thing exists for pip. diff --git a/results/classifier/118/all/1317603 b/results/classifier/118/all/1317603 new file mode 100644 index 00000000..741a4d1f --- /dev/null +++ b/results/classifier/118/all/1317603 @@ -0,0 +1,215 @@ +permissions: 0.985 +register: 0.977 +graphic: 0.975 +virtual: 0.972 +semantic: 0.971 +debug: 0.971 +arm: 0.969 +kernel: 0.969 +assembly: 0.967 +architecture: 0.967 +socket: 0.967 +device: 0.965 +performance: 0.965 +boot: 0.957 +files: 0.953 +PID: 0.952 +network: 0.948 +KVM: 0.935 +hypervisor: 0.931 +risc-v: 0.928 +peripherals: 0.927 +vnc: 0.922 +TCG: 0.914 +ppc: 0.913 +VMM: 0.903 +user-level: 0.895 +x86: 0.864 +mistranslation: 0.861 +i386: 0.831 + +qemu-system-ppc does not terminate on VM exit + +When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. + +The qemu-system-ppc process must be killed. + +ProblemType: Bug +DistroRelease: Ubuntu 14.04 +Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 +ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 +Uname: Linux 3.13.9+ ppc +ApportVersion: 2.14.1-0ubuntu3 +Architecture: powerpc +Date: Thu May 8 12:20:57 2014 +ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=<set> + LANG=en_US.UTF-8 + SHELL=/bin/bash +SourcePackage: qemu +UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) + + + +What do you mean by "cannot be rebooted"? When you log into the guest and type "reboot", nothing happens? Does init call reboot(2) and the kernel ignores it? All of userspace is properly terminated, and kernel hangs at the actual reboot? + +qemu-system-ppc never terminates. + + +Regards, + John. + +-- + +o Energy-efficiency is #1 reason data centers look to expand. -- +Digital Realty Trust +o Green Data Centers spending to increase 300% worldwide by 2016. -- +Pike Research +o Data Centers have become as vital to the functioning of society as +power stations. -- The Economist + + +On Sat, May 24, 2014 at 5:35 PM, Serge Hallyn +<email address hidden> wrote: +> What do you mean by "cannot be rebooted"? When you log into the guest +> and type "reboot", nothing happens? Does init call reboot(2) and the +> kernel ignores it? All of userspace is properly terminated, and kernel +> hangs at the actual reboot? +> +> ** Also affects: qemu +> Importance: Undecided +> Status: New +> +> -- +> You received this bug notification because you are subscribed to the bug +> report. +> https://bugs.launchpad.net/bugs/1317603 +> +> Title: +> qemu-system-ppc does not terminate on VM exit +> +> Status in QEMU: +> New +> Status in “qemu” package in Ubuntu: +> New +> +> Bug description: +> When a VM is created for a p4080-e500mc ; the VM can not be rebooted +> or terminated. +> +> The qemu-system-ppc process must be killed. +> +> ProblemType: Bug +> DistroRelease: Ubuntu 14.04 +> Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 +> ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 +> Uname: Linux 3.13.9+ ppc +> ApportVersion: 2.14.1-0ubuntu3 +> Architecture: powerpc +> Date: Thu May 8 12:20:57 2014 +> ProcEnviron: +> TERM=xterm +> PATH=(custom, no user) +> XDG_RUNTIME_DIR=<set> +> LANG=en_US.UTF-8 +> SHELL=/bin/bash +> SourcePackage: qemu +> UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) +> +> To manage notifications about this bug go to: +> https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions + + +Quoting <email address hidden> (<email address hidden>): +> qemu-system-ppc never terminates. + +Assuming you are using the same scripts as in the other bugs, you are passing +-no-shutdown to qemu, asking it to not exit when the guest exits. If you +want qemu to exit when the guest is done, then please remove that flag, and +see if that fixes it. + +If you are then manually killing qemu before the guest is done running, that +would also explain why the guest fs is corrupted. + + +It does not change the the behaviour. +With or without those options the VM qemu-system-ppc session never exits. + + + +Regards, + John. + +-- + +o Energy-efficiency is #1 reason data centers look to expand. -- +Digital Realty Trust +o Green Data Centers spending to increase 300% worldwide by 2016. -- +Pike Research +o Data Centers have become as vital to the functioning of society as +power stations. -- The Economist + + +On Sat, May 24, 2014 at 7:12 PM, Serge Hallyn +<email address hidden> wrote: +> Quoting <email address hidden> (<email address hidden>): +>> qemu-system-ppc never terminates. +> +> Assuming you are using the same scripts as in the other bugs, you are passing +> -no-shutdown to qemu, asking it to not exit when the guest exits. If you +> want qemu to exit when the guest is done, then please remove that flag, and +> see if that fixes it. +> +> If you are then manually killing qemu before the guest is done running, that +> would also explain why the guest fs is corrupted. +> +> -- +> You received this bug notification because you are subscribed to the bug +> report. +> https://bugs.launchpad.net/bugs/1317603 +> +> Title: +> qemu-system-ppc does not terminate on VM exit +> +> Status in QEMU: +> New +> Status in “qemu” package in Ubuntu: +> New +> +> Bug description: +> When a VM is created for a p4080-e500mc ; the VM can not be rebooted +> or terminated. +> +> The qemu-system-ppc process must be killed. +> +> ProblemType: Bug +> DistroRelease: Ubuntu 14.04 +> Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 +> ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 +> Uname: Linux 3.13.9+ ppc +> ApportVersion: 2.14.1-0ubuntu3 +> Architecture: powerpc +> Date: Thu May 8 12:20:57 2014 +> ProcEnviron: +> TERM=xterm +> PATH=(custom, no user) +> XDG_RUNTIME_DIR=<set> +> LANG=en_US.UTF-8 +> SHELL=/bin/bash +> SourcePackage: qemu +> UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) +> +> To manage notifications about this bug go to: +> https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions + + +I've uploaded a build of today's qemu git HEAD to https://launchpad.net/~ubuntu-virt/+archive/virt-daily-upstream . Would it be possible to test with that? I assume you'll need to grab the source and re-build packages for ppc. + +I am no longer working on this project, + +Looking at comment #7, it sounds like you're not interested in this ticket anymore, so I'm closing it as "Won't fix". Feel free to open it again if you are still interested in this. + +[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] + |