[Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by N

qemu-commits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by N

From:	Peter Maydell
Subject:	[Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by NANOSECONDS_PE...
Date:	Tue, 13 Oct 2020 05:00:37 -0700
  Branch: refs/heads/staging
  Home:   https://github.com/qemu/qemu
  Commit: 4f3ccd4f166c12ae2bbdf21af3a16da8a7f16a78
      
https://github.com/qemu/qemu/commit/4f3ccd4f166c12ae2bbdf21af3a16da8a7f16a78
  Author: Philippe Mathieu-Daudé <f4bug@amsat.org>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M tests/qtest/rtc-test.c

  Log Message:
  -----------
  tests/qtest: Replace magic value by NANOSECONDS_PER_SECOND definition

Use self-explicit NANOSECONDS_PER_SECOND definition instead
of a magic value.

Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20201011194918.3219195-5-f4bug@amsat.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 320c6e78930e588c548f7bfe84f43fe5dfe2e5ad
      
https://github.com/qemu/qemu/commit/320c6e78930e588c548f7bfe84f43fe5dfe2e5ad
  Author: Alexander Bulekov <alxndr@bu.edu>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M .gitlab-ci.yml

  Log Message:
  -----------
  gitlab-ci.yml: Only run one test-case per fuzzer

With 1000 runs, there is a non-negligible chance that the fuzzer can
trigger a crash. With this CI job, we care about catching build/runtime
issues in the core fuzzing code. Actual device fuzzing takes place on
oss-fuzz. For these purposes, only running one input should be
sufficient.

Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Suggested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20201002143524.56930-1-alxndr@bu.edu>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: d44d9b6bc81df6080ed83073ab2711e5a4258a07
      
https://github.com/qemu/qemu/commit/d44d9b6bc81df6080ed83073ab2711e5a4258a07
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M tests/requirements.txt

  Log Message:
  -----------
  Acceptance tests: bump pycdlib version for easier installation

On with certain versions of "pip", package installations will attempt
to create wheels.  And, on environments without a "complete" Python
installation (as described in the acceptance tests requirements docs),
that will fail.

pycdlib, starting with version 1.11.0, is now being made available
as wheels, so its instalation on those constrained environments is
now possible.

Buglink: https://bugs.launchpad.net/qemu/+bug/1897783
Reported-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20201009205513.751968-2-crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 52dff285698a3c9c7d97d8a790439a16f5fdb038
      
https://github.com/qemu/qemu/commit/52dff285698a3c9c7d97d8a790439a16f5fdb038
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M .gitlab-ci.yml

  Log Message:
  -----------
  Acceptance tests: do not show canceled test logs on GitLab CI

Tests resulting in "CANCEL" in Avocado are usually canceled on
purpose, and are almost identical to "SKIP".  The logs for canceled
tests are adding a lot of noise to the logs being shown on GitLab CI,
and causing distraction from real failures.

As a side note, this "after script" is scheduled for removal once the
feature is implemented within Avocado itself.

Reference: https://github.com/avocado-framework/avocado/issues/4266
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20201009205513.751968-3-crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: ec4d2feb27c5e46a69e2c2d588e982c9327e325e
      
https://github.com/qemu/qemu/commit/ec4d2feb27c5e46a69e2c2d588e982c9327e325e
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M .gitlab-ci.yml

  Log Message:
  -----------
  Acceptance tests: show test report on GitLab CI

Avocado will, by default, produce JUnit files.  Let's ask GitLab
to present those in the web UI.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20201009205513.751968-4-crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: d8dd10950199ee4a505dc4872171dcb1b4ca6710
      
https://github.com/qemu/qemu/commit/d8dd10950199ee4a505dc4872171dcb1b4ca6710
  Author: Li Qiang <liq3ea@163.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    A tests/qtest/fuzz-test.c
    M tests/qtest/meson.build

  Log Message:
  -----------
  qtest: add fuzz test case

Currently the device fuzzer finds more and more issues.
For every fuzz case, we need not only the fixes but also
the corresponding test case. We can analysis the reproducer
for every case and find what happened in where and write
a beautiful test case. However the raw data of reproducer is not
friendly to analysis. It will take a very long time, even far more
than the fixes itself. So let's create a new file to hold all of
the fuzz test cases and just use the raw data to act as the test
case. This way nobody will be afraid of writing a test case for
the fuzz reproducer.

This patch adds the issue LP#1878263 test case.

Signed-off-by: Li Qiang <liq3ea@163.com>
Message-Id: <20200921160605.19329-1-liq3ea@163.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
[thuth: Slightly adjusted commit message, removed empty lines]
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: a4339de2de4def4beb33e22e6f506bcc8b9d9326
      
https://github.com/qemu/qemu/commit/a4339de2de4def4beb33e22e6f506bcc8b9d9326
  Author: Dr. David Alan Gilbert <dgilbert@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M tests/qtest/migration-test.c

  Log Message:
  -----------
  tests/migration: Allow longer timeouts

In travis, with gcov and gprof we're seeing timeouts; hopefully fix
this by increasing the test timeouts a bit, but for xbzrle ensure it
really does get a couple of cycles through to test the cache.

I think the problem in travis is we have about 2 host CPU threads,
in the test we have at least 3:
   a) The vCPU thread (100% flat out)
   b) The source migration thread
   c) The destination migration thread

if (b) & (c) are slow for any reason - gcov+gperf or a slow host -
then they're sharing one host CPU thread so limit the migration
bandwidth.

Tested on my laptop with:
   taskset -c 0,1 ./tests/qtest/migration-test -p /x86_64/migration

Reported-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20201008160330.130431-1-dgilbert@redhat.com>
[thuth: Move the #define to the right location]
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: eaf65114f0585a914642c1ce1379bb8339984858
      
https://github.com/qemu/qemu/commit/eaf65114f0585a914642c1ce1379bb8339984858
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M softmmu/vl.c

  Log Message:
  -----------
  softmmu/vl: Be less verbose about missing KVM when running the qtests

Some of the qtests use "-accel kvm -accel tcg" to run real guest code.
This causes some error messages when kvm is not available. We do not
really care about these messages since the fallback to tcg is expected
here. So let's silence them to avoid that they spoil the output of
the tests.

Unfortunately, we can not use the qtest_enabled() wrapper in this case,
since the qtest accelerator itself is not initialized. Thus we have to
test for the qtest_chrdev variable instead.

Message-Id: <20200710085020.28222-1-thuth@redhat.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 07f5903c852de10fa71059f5e7594d203e077b10
      
https://github.com/qemu/qemu/commit/07f5903c852de10fa71059f5e7594d203e077b10
  Author: Ani Sinha <ani@anisinha.ca>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M tests/qtest/bios-tables-test.c

  Log Message:
  -----------
  Add a comment in bios-tables-test.c to clarify the reason behind approach

A comment is added in bios-tables-test.c that explains the reasoning
behind the process of updating the ACPI table blobs when new tests are added
or old tests are modified or code is committed that affect tests. The
explanation would help future contributors follow the correct process when
making code changes that affect ACPI tables.

Signed-off-by: Ani Sinha <ani@anisinha.ca>
Acked-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <20200929142501.1057-1-ani@anisinha.ca>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 520ddc18bf55fbd7c7409c737b1cd7e8b1e7c971
      
https://github.com/qemu/qemu/commit/520ddc18bf55fbd7c7409c737b1cd7e8b1e7c971
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M MAINTAINERS

  Log Message:
  -----------
  MAINTAINERS: Ignore bios-tables-test in the qtest section

I'm very often getting CC: on rather large patch series that
modify the ACPI stuff of either ARM or x86, just because the
bios-table-test is often slightly involved here. I can't say
much about ACPI, and the bios-table-test is already covered
by the ACPI section in MAINTAINERS, so I'd rather prefer to
not getting automatically CC-ed on such patch series anymore.
If people want my opinion about qtest-related changes, they
can still put me on CC manually.

Message-Id: <20201001042717.136033-1-thuth@redhat.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 2ae00c8b2f7536f1bb38c3eb40d76f4196c61d0c
      
https://github.com/qemu/qemu/commit/2ae00c8b2f7536f1bb38c3eb40d76f4196c61d0c
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    R pc-bios/keymaps/.gitignore
    R plugins/.gitignore
    R tests/.gitignore
    R tests/fp/.gitignore
    R tests/migration/.gitignore
    R tests/multiboot/.gitignore
    R tests/qemu-iotests/.gitignore
    R tests/tcg/.gitignore
    R tests/uefi-test-tools/.gitignore

  Log Message:
  -----------
  Remove superfluous .gitignore files

Since we are now always doing out-of-tree builds, these gitignore
files should not be necessary anymore.

Message-Id: <20200919133637.72744-1-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 4258c8e221682652e9b9095c29406f91124d86f7
      
https://github.com/qemu/qemu/commit/4258c8e221682652e9b9095c29406f91124d86f7
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M docs/system/deprecated.rst

  Log Message:
  -----------
  docs/system/deprecated: Mark the 'moxie' CPU as deprecated

It is currently unclear whether anybody is still using the 'moxie' CPU,
and there are no images for testing available this CPU, so the code has
likely bit-rotten in the course of time. When I asked the maintainer
for information, I did not get a reply within four weeks yet (see
https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg07201.html).
The last Signed-off-by line from Anthony in our repo is from 2013,
so it seems like this code is rather unmaintained. Time to put it onto
the deprecation list to see whether somebody is still interested in this
code or whether we could remove it in a couple of releases.

Message-Id: <20200923171815.97801-1-thuth@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 5f8937d63f5b24bbe044c6e00519fa91f86f04bc
      
https://github.com/qemu/qemu/commit/5f8937d63f5b24bbe044c6e00519fa91f86f04bc
  Author: Yonggang Luo <luoyonggang@gmail.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M configure

  Log Message:
  -----------
  configure: fixes indent of $meson setup

convert these line from tab to space

Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20201012234348.1427-2-luoyonggang@gmail.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 1f47547256b72fecd9ebf629a8e48cd20282a758
      
https://github.com/qemu/qemu/commit/1f47547256b72fecd9ebf629a8e48cd20282a758
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    A .gitlab-ci.d/check-patch.py
    M .gitlab-ci.yml

  Log Message:
  -----------
  gitlab: add a CI job for running checkpatch.pl

This job is advisory since it is expected that certain patches will fail
the style checks and checkpatch.pl provides no way to mark exceptions to
the rules.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20200918132903.1848939-2-berrange@redhat.com>
[thuth: Use "stage: build" to let it run earlier]
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 34ed46a2845df4305aa35c22ea517b4241faae06
      
https://github.com/qemu/qemu/commit/34ed46a2845df4305aa35c22ea517b4241faae06
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    A .gitlab-ci.d/check-dco.py
    M .gitlab-ci.yml

  Log Message:
  -----------
  gitlab: add a CI job to validate the DCO sign off

While checkpatch.pl can validate DCO sign off that job must always be
advisory only since it is expected that certain patches will fail some
code style rules.

We require the DCO sign off to be mandatory for all commits though, so
it benefits from being validated in a standalone job.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20200918132903.1848939-3-berrange@redhat.com>
[thuth: Use "stage: build" to let it run earlier]
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 4fb716360a6c19d1860dd312ebd3404ca499a186
      
https://github.com/qemu/qemu/commit/4fb716360a6c19d1860dd312ebd3404ca499a186
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M MAINTAINERS

  Log Message:
  -----------
  gitlab: assign python helper files to GitLab maintainers section

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20200918132903.1848939-4-berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: d914375070dc67dead065425fc3e3633fea4e0d3
      
https://github.com/qemu/qemu/commit/d914375070dc67dead065425fc3e3633fea4e0d3
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: make branch name configurable

With the utility function `get_local_staging_branch_commit()`, the
name of the branch is hard coded (including in the function name).

For extensibility reasons, let's make that configurable.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-2-crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 6dfcbff8bf7ca8c52a5ee2d351ec9c291e22fd5e
      
https://github.com/qemu/qemu/commit/6dfcbff8bf7ca8c52a5ee2d351ec9c291e22fd5e
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: improve message regarding timeout

The script has its own timeout, which is about how long the script
will wait (when called with --wait) for the pipeline to complete, and
not necessarily for the pipeline to complete.

Hopefully this new wording will be clearer.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-3-crosa@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: db5424dfda1329da226ad98904c3a26fc9f7310f
      
https://github.com/qemu/qemu/commit/db5424dfda1329da226ad98904c3a26fc9f7310f
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: give early feedback on running pipelines

When waiting for a pipeline to run and finish, it's better to give
early feedback, and then sleep and wait, than the other wait around.

Specially for the first iteration, it's frustrating to see nothing
while the script is sleeping.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-4-crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 91641d555ae06726169f6ec8b57caeebcb0b71d0
      
https://github.com/qemu/qemu/commit/91641d555ae06726169f6ec8b57caeebcb0b71d0
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: refactor parser creation

Out of the main function.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-5-crosa@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 79df438eeb5e754a0ae22210238e4e6555e7428f
      
https://github.com/qemu/qemu/commit/79df438eeb5e754a0ae22210238e4e6555e7428f
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: handle keyboard interrupts

So that exits based on user requests are handled more gracefully.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-6-crosa@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 176498ab57dc14a7c14a58b490aa16319f0cf638
      
https://github.com/qemu/qemu/commit/176498ab57dc14a7c14a58b490aa16319f0cf638
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: use more descriptive exceptions

For two very different error conditions.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-7-crosa@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: ea8bf1e514d2f442dd1a008794eb1563e2ee1c48
      
https://github.com/qemu/qemu/commit/ea8bf1e514d2f442dd1a008794eb1563e2ee1c48
  Author: Cleber Rosa <crosa@redhat.com>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    M scripts/ci/gitlab-pipeline-status

  Log Message:
  -----------
  scripts/ci/gitlab-pipeline-status: wait for pipeline creation

When called in wait mode, this script will also wait for the pipeline
to be get to a "running" state.  Because many more status may be seen
until a pipeline gets to "running", and those need to be handle too.

Reference: https://docs.gitlab.com/ee/api/pipelines.html#list-project-pipelines
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200904164258.240278-8-crosa@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: b37da837630ca7cdbc45de4c5339bbfc6d21beed
      
https://github.com/qemu/qemu/commit/b37da837630ca7cdbc45de4c5339bbfc6d21beed
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2020-10-13 (Tue, 13 Oct 2020)

  Changed paths:
    A .gitlab-ci.d/check-dco.py
    A .gitlab-ci.d/check-patch.py
    M .gitlab-ci.yml
    M MAINTAINERS
    M configure
    M docs/system/deprecated.rst
    R pc-bios/keymaps/.gitignore
    R plugins/.gitignore
    M scripts/ci/gitlab-pipeline-status
    M softmmu/vl.c
    R tests/.gitignore
    R tests/fp/.gitignore
    R tests/migration/.gitignore
    R tests/multiboot/.gitignore
    R tests/qemu-iotests/.gitignore
    M tests/qtest/bios-tables-test.c
    A tests/qtest/fuzz-test.c
    M tests/qtest/meson.build
    M tests/qtest/migration-test.c
    M tests/qtest/rtc-test.c
    M tests/requirements.txt
    R tests/tcg/.gitignore
    R tests/uefi-test-tools/.gitignore

  Log Message:
  -----------
  Merge remote-tracking branch 
'remotes/huth-gitlab/tags/pull-request-2020-10-13' into staging

* qtest improvements (test for crash found with the fuzzer, increase
  downtime in migration test, less verbose output when running w/o KVM)
* Improve handling of acceptance tests in the Gitlab-CI
* Run checkpatch.pl in the Gitlab-CI
* Improve the gitlab-pipeline-status script
* Misc patches (mark 'moxie' as deprecated, remove stale .gitignore files, ...)

# gpg: Signature made Tue 13 Oct 2020 11:49:06 BST
# gpg:                using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
# gpg:                issuer "thuth@redhat.com"
# gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
# gpg:                 aka "Thomas Huth <thuth@redhat.com>" [full]
# gpg:                 aka "Thomas Huth <huth@tuxfamily.org>" [full]
# gpg:                 aka "Thomas Huth <th.huth@posteo.de>" [unknown]
# Primary key fingerprint: 27B8 8847 EEE0 2501 18F3  EAB9 2ED9 D774 FE70 2DB5

* remotes/huth-gitlab/tags/pull-request-2020-10-13: (23 commits)
  scripts/ci/gitlab-pipeline-status: wait for pipeline creation
  scripts/ci/gitlab-pipeline-status: use more descriptive exceptions
  scripts/ci/gitlab-pipeline-status: handle keyboard interrupts
  scripts/ci/gitlab-pipeline-status: refactor parser creation
  scripts/ci/gitlab-pipeline-status: give early feedback on running pipelines
  scripts/ci/gitlab-pipeline-status: improve message regarding timeout
  scripts/ci/gitlab-pipeline-status: make branch name configurable
  gitlab: assign python helper files to GitLab maintainers section
  gitlab: add a CI job to validate the DCO sign off
  gitlab: add a CI job for running checkpatch.pl
  configure: fixes indent of $meson setup
  docs/system/deprecated: Mark the 'moxie' CPU as deprecated
  Remove superfluous .gitignore files
  MAINTAINERS: Ignore bios-tables-test in the qtest section
  Add a comment in bios-tables-test.c to clarify the reason behind approach
  softmmu/vl: Be less verbose about missing KVM when running the qtests
  tests/migration: Allow longer timeouts
  qtest: add fuzz test case
  Acceptance tests: show test report on GitLab CI
  Acceptance tests: do not show canceled test logs on GitLab CI
  ...

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


Compare: https://github.com/qemu/qemu/compare/71bd66746084...b37da837630c
[Prev in Thread]
Current Thread
[Next in Thread]
[Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by NANOSECONDS_PE..., Peter Maydell <=
- [Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by NANOSECONDS_PE..., Peter Maydell, 2020/10/13
Prev by Date: [Qemu-commits] [qemu/qemu] a64627: qemu-img-cmds.hx: Update comment that mentions Tex...
Next by Date: [Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by NANOSECONDS_PE...
Previous by thread: [Qemu-commits] [qemu/qemu] a64627: qemu-img-cmds.hx: Update comment that mentions Tex...
Next by thread: [Qemu-commits] [qemu/qemu] 4f3ccd: tests/qtest: Replace magic value by NANOSECONDS_PE...
Index(es):
- Date
- Thread