On 8 February 2017 at 08:47, Thomas Huth <th...@redhat.com> wrote: > How fast is that aarch64 machine?
It's a juno board, so it's not very fast, but I wouldn't have expected it to hit a 100 second timeout assuming the test isn't trying to do a ludicrous amount of work. > The timeout of the prom-env test is > already 100 seconds, so that seems to be plenty to me (the test normally > finishes here on my laptop within 15 seconds). > OTOH, if it helps with the aarch64 machine, I'm also fine if we increase > the timeout further - but what value would be appropriate then? Could you > please run the following on that slow machine: > > time QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 tests/prom-env-test /ppc64/prom-env/mac99: OK /ppc64/prom-env/g3beige: OK /ppc64/prom-env/pseries: OK real 1m37.657s user 1m36.748s sys 0m1.440s Breaking that down per testcase: <tmmu/qemu-system-ppc64 tests/prom-env-test -v -p /ppc64/prom-env/mac99 /ppc64/prom-env/mac99: OK real 0m9.836s user 0m9.584s sys 0m0.424s <u/qemu-system-ppc64 tests/prom-env-test -v -p /ppc64/prom-env/g3beige /ppc64/prom-env/g3beige: OK real 0m9.099s user 0m8.988s sys 0m0.144s <qemu-system-ppc64 tests/prom-env-test -v -p /ppc64/prom-env/pseries /ppc64/prom-env/pseries: OK real 1m24.362s user 1m23.572s sys 0m1.144s pseries is much slower than the other two and at 85 seconds is not all that much below the 100s. Something's odd here. thanks -- PMM
