testing/next (rcutorture and misc tweaks)

[PATCH v1 0/5] testing/next (rcutorture and misc tweaks)

Alex Bennée posted 5 patches 5 years, 9 months ago

Download series mbox

Test FreeBSD passed

Test docker-quick@centos7 passed

Test docker-mingw@fedora passed

Test checkpatch passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20200207113939.9247-1-alex.bennee@linaro.org

Maintainers: Cornelia Huck <cohuck@redhat.com>

tests/rcutorture.c                        | 55 +++++++++++++++++------
.travis.yml                               | 10 +++++
tests/tcg/aarch64/Makefile.softmmu-target |  2 +
3 files changed, 53 insertions(+), 14 deletions(-)

Expand all Fold all

[PATCH v1 0/5] testing/next (rcutorture and misc tweaks)

Posted by Alex Bennée 5 years, 9 months ago

Hi,

The current state of testing/next is mostly a rubber duck exercise as
I tried to figure out what might cause the rcutorture test to fail.
The only real practical change is asserting we are never about to
reset and existing active RCU structure. So far I haven't seen the
rcutorture crash occur since (although git stability seems to be a
current problem for Travis).

Alex Bennée (4):
  tests/tcg: include a skip runner for pauth3 with plugins
  tests/rcutorture: update usage hint
  tests/rcutorture: better document locking of stats
  tests/rcutorture: mild documenting refactor of update thread

Thomas Huth (1):
  travis.yml: Test the s390-ccw build, too

 tests/rcutorture.c                        | 55 +++++++++++++++++------
 .travis.yml                               | 10 +++++
 tests/tcg/aarch64/Makefile.softmmu-target |  2 +
 3 files changed, 53 insertions(+), 14 deletions(-)

-- 
2.20.1

Re: [PATCH v1 0/5] testing/next (rcutorture and misc tweaks)

Posted by Alex Bennée 5 years, 9 months ago

Alex Bennée <alex.bennee@linaro.org> writes:

> Hi,
>
> The current state of testing/next is mostly a rubber duck exercise as
> I tried to figure out what might cause the rcutorture test to fail.
> The only real practical change is asserting we are never about to
> reset and existing active RCU structure. So far I haven't seen the
> rcutorture crash occur since (although git stability seems to be a
> current problem for Travis).
>
> Alex Bennée (4):
>   tests/tcg: include a skip runner for pauth3 with plugins
>   tests/rcutorture: update usage hint
>   tests/rcutorture: better document locking of stats
>   tests/rcutorture: mild documenting refactor of update thread
>
> Thomas Huth (1):
>   travis.yml: Test the s390-ccw build, too
>
>  tests/rcutorture.c                        | 55 +++++++++++++++++------
>  .travis.yml                               | 10 +++++
>  tests/tcg/aarch64/Makefile.softmmu-target |  2 +
>  3 files changed, 53 insertions(+), 14 deletions(-)

Ping?

I'm particularly interested in the rcutorture changes which so far have
not yielded any:

  ERROR:/home/travis/build/qemu/qemu/tests/rcutorture.c:384:gtest_stress: assertion failed (n_mberror == 0): (1 == 0)

in my various test trees.

-- 
Alex Bennée