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
