e.g. https://buildbot.mariadb.org/#/builders/327/builds/23484
sys_vars.session_track_system_variables_basic w12 [ fail ]
|
Test ended at 2024-09-10 07:29:00
|
|
CURRENT_TEST: sys_vars.session_track_system_variables_basic
|
--- /home/buildbot/s390x-rhel-8/build/mysql-test/suite/sys_vars/r/session_track_system_variables_basic.result 2024-09-10 05:26:18.000000000 +0000
|
+++ /home/buildbot/s390x-rhel-8/build/mysql-test/suite/sys_vars/r/session_track_system_variables_basic.reject 2024-09-10 07:29:00.405736302 +0000
|
@@ -158,16 +158,16 @@
|
set global session_track_system_variables="autocommit,character_set_client,character_set_connection,redirect_url,time_zone";
|
connect foo,localhost,root;
|
-- Tracker : SESSION_TRACK_SYSTEM_VARIABLES
|
--- autocommit
|
--- ON
|
+-- redirect_url
|
+--
|
-- time_zone
|
-- SYSTEM
|
-- character_set_client
|
-- latin1
|
+-- autocommit
|
+-- ON
|
-- character_set_connection
|
-- latin1
|
--- redirect_url
|
---
|
According to danblack it could be caused by the output coming out of a hash inside the server, and that one solution is to sort the output in client/mysqltest.cc
The reason that the failure only appears after the MDEV-31609 testcase is because it was the first to output multiple variables in the session track info.
Bug
Major
MDEV-33073 always green buildbot
