[Qemu-commits] [qemu/qemu] d24279: tests/docker: Include 'ccache' in Debian base image

[Peter Maydell]

  Branch: refs/heads/staging
  Home:   https://github.com/qemu/qemu
  Commit: d2427956e1735ebda99ff408dc99d3eb4e6ada40
      
https://github.com/qemu/qemu/commit/d2427956e1735ebda99ff408dc99d3eb4e6ada40
  Author: Philippe Mathieu-Daudé <f4bug@amsat.org>
  Date:   2021-01-06 (Wed, 06 Jan 2021)

  Changed paths:
    M tests/docker/dockerfiles/debian10.docker

  Log Message:
  -----------
  tests/docker: Include 'ccache' in Debian base image

Include the 'ccache' package to speed up compilation.

Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20201213211601.253530-1-f4bug@amsat.org>
Fixes: d6db2a1cdf ("docker: add debian-buster-arm64-cross")
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>


  Commit: f4c6557bfef388628f50af35d36be85c30ab2553
      
https://github.com/qemu/qemu/commit/f4c6557bfef388628f50af35d36be85c30ab2553
  Author: Alex Bennée <alex.bennee@linaro.org>
  Date:   2021-01-06 (Wed, 06 Jan 2021)

  Changed paths:
    M tests/qemu-iotests/group

  Log Message:
  -----------
  tests/iotests: drop test 312 from auto group

The "auto" documentation states:

  That means they should run with every QEMU binary (also non-x86)

which is not the case as the check-system-fedora build which only
includes a rag tag group of rare and deprecated targets doesn't
support the virtio device required.

Fixes: ef9bba1484b ("quorum: Implement bdrv_co_block_status()")
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210105100402.12350-1-alex.bennee@linaro.org>


  Commit: 93eaabde61cf048660a01dc2b5f55c061fd73e6b
      
https://github.com/qemu/qemu/commit/93eaabde61cf048660a01dc2b5f55c061fd73e6b
  Author: Alex Bennée <alex.bennee@linaro.org>
  Date:   2021-01-06 (Wed, 06 Jan 2021)

  Changed paths:
    M tests/acceptance/machine_s390_ccw_virtio.py

  Log Message:
  -----------
  tests/acceptance: bound the size of readline in s390_ccw_virtio

The read binary data as text via a PPM export of the frame buffer
seems a bit sketchy and it did blow up in the real world when the
assertion failed:

  https://gitlab.com/qemu-project/qemu/-/jobs/943183183

However short of cleaning up the test to be more binary focused at
least limit the attempt to dump the whole file as hexified zeros in
the logs.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20210105124405.15424-1-alex.bennee@linaro.org>


  Commit: af229fc367021e361cebaf84acceb01f28922cc4
      
https://github.com/qemu/qemu/commit/af229fc367021e361cebaf84acceb01f28922cc4
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2021-01-06 (Wed, 06 Jan 2021)

  Changed paths:
    M .cirrus.yml

  Log Message:
  -----------
  cirrus: don't run full qtest on macOS

The Cirrus CI macOS build hosts have exhibited a serious performance
degradation in recent months. For example the "qom-test" qtest takes
over an hour for only the qemu-system-aarch64 binary. This is as much
20-40 times slower than other environments. The other qtests all show
similar performance degradation, as do many of the unit tests.

This does not appear related to QEMU code changes, since older git
commits which were known to fully complete in less than 1 hour on
Cirrus CI now also show similar bad performance. Either Cirrus CI
performance has degraded, or an change in its environment has exposed
a latent bug widely affecting all of QEMU. Debugging the qom-test
showed no easily identified large bottleneck - every step of the
test execution was simply slower.

macOS builds/tests run outside Cirrus CI show normal performance.

With an inability to identify any obvious problem, the only viable
way to get a reliably completing Cirrus CI macOS job is to cut out
almost all of the qtests. We choose to run the x86_64 target only,
since that has very few machine types and thus is least badly
impacted in the qom-test execution.

With this change, the macOS jobs complete in approx 35 minutes.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Message-Id: <20210106114159.981538-1-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>


  Commit: 470dd6bd360782f5137f7e3376af6a44658eb1d3
      
https://github.com/qemu/qemu/commit/470dd6bd360782f5137f7e3376af6a44658eb1d3
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2021-01-06 (Wed, 06 Jan 2021)

  Changed paths:
    M .cirrus.yml
    M tests/acceptance/machine_s390_ccw_virtio.py
    M tests/docker/dockerfiles/debian10.docker
    M tests/qemu-iotests/group

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/stsquad/tags/pull-testing-060121-4' 
into staging

Testing updates (back to green)

  - include ccache in Debian 10 docker image
  - iotests: drop 312 from auto group
  - bound reading of s390x framebuffer file
  - cirrus: drop non-x86 tests so we complete

# gpg: Signature made Wed 06 Jan 2021 17:31:14 GMT
# gpg:                using RSA key 6685AE99E75167BCAFC8DF35FBD0DB095A9E2A44
# gpg: Good signature from "Alex Bennée (Master Work Key) 
<alex.bennee@linaro.org>" [full]
# Primary key fingerprint: 6685 AE99 E751 67BC AFC8  DF35 FBD0 DB09 5A9E 2A44

* remotes/stsquad/tags/pull-testing-060121-4:
  cirrus: don't run full qtest on macOS
  tests/acceptance: bound the size of readline in s390_ccw_virtio
  tests/iotests: drop test 312 from auto group
  tests/docker: Include 'ccache' in Debian base image

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


Compare: https://github.com/qemu/qemu/compare/aadac5b3d9fd...470dd6bd3607