[MDEV-22962] perfschema.show_aggregate fails in buildbot with variety of wrong results Created: 2020-06-19  Updated: 2023-10-07

Status: Open
Project: MariaDB Server
Component/s: Performance Schema, Tests
Affects Version/s: 10.5
Fix Version/s: 10.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-26207 perfschema.show_aggregate,innodb,pot ... Open

 Description   

http://buildbot.askmonty.org/buildbot/builders/bld-p9-rhel7/builds/4392

10.5 e341fb0dae1008b98d6fc96f8847e6f1

 
perfschema.show_aggregate 'innodb,pot'   w58 [ fail ]
 
        Test ended at 2020-06-19 16:09:14
 
 
 
CURRENT_TEST: perfschema.show_aggregate
 
--- /opt/buildbot-slave/bld-p9-rhel7/build/mysql-test/suite/perfschema/r/show_aggregate.result	2020-06-18 01:58:32.718011905 +0300
 
+++ /opt/buildbot-slave/bld-p9-rhel7/build/mysql-test/suite/perfschema/r/show_aggregate.reject	2020-06-19 16:09:14.630545946 +0300
 
@@ -203,12 +203,6 @@
 
 USE performance_schema;
 
 SELECT * FROM status_by_thread WHERE thread_id IN (@con1_id, @con2_id, @con3_id) AND variable_name IN ('handler_delete', 'handler_rollback') ORDER BY thread_id;
 
 THREAD_ID	VARIABLE_NAME	VARIABLE_VALUE
 
-thread_id	Handler_delete	1
 
-thread_id	Handler_rollback	1
 
-thread_id	Handler_delete	2
 
-thread_id	Handler_rollback	2
 
-thread_id	Handler_delete	3
 
-thread_id	Handler_rollback	3
 
 #
 
 # Verify expected counts for 'handler_delete' per thread
 
 # 
 
 
mysqltest: Result length mismatch

10.5 4243785f288149fc1571b168cda1c921

 
perfschema.show_aggregate '1tpc,innodb'  w2 [ fail ]
 
        Test ended at 2020-06-19 12:34:54
 
 
 
CURRENT_TEST: perfschema.show_aggregate
 
--- /usr/share/mysql-test/suite/perfschema/r/show_aggregate.result	2020-06-19 09:07:03.000000000 +0000
 
+++ /dev/shm/var/2/log/show_aggregate.reject	2020-06-19 12:34:54.397024241 +0000
 
@@ -505,17 +505,17 @@
 
 SELECT * FROM status_by_account WHERE user IN ('user1', 'user2', 'user3') AND variable_name IN ('handler_delete');
 
 USER	HOST	VARIABLE_NAME	VARIABLE_VALUE
 
 user1	localhost	Handler_delete	0
 
-user2	localhost	Handler_delete	0
 
+user2	localhost	Handler_delete	2
 
 user3	localhost	Handler_delete	0
 
 #
 
 SELECT * FROM status_by_host WHERE host IN ('localhost') AND variable_name IN ('handler_delete');
 
 HOST	VARIABLE_NAME	VARIABLE_VALUE
 
-localhost	Handler_delete	0
 
+localhost	Handler_delete	2
 
 #
 
 SELECT * FROM status_by_user WHERE user IN ('user1', 'user2', 'user3') AND variable_name IN ('handler_delete');
 
 USER	VARIABLE_NAME	VARIABLE_VALUE
 
 user1	Handler_delete	0
 
-user2	Handler_delete	0
 
+user2	Handler_delete	2
 
 user3	Handler_delete	0
 
 # ================================================================================
 
 # CLEANUP
 
 
 
mysqltest: Result content mismatch

10.5 bd62a636a42f1486437cbed21198315f

 
perfschema.show_aggregate 'innodb,pot'   w2 [ fail ]
 
        Test ended at 2020-06-16 23:14:13
 
 
 
CURRENT_TEST: perfschema.show_aggregate
 
--- /mnt/buildbot/build/mariadb-10.5.4/mysql-test/suite/perfschema/r/show_aggregate.result	2020-06-16 22:04:48.000000000 -0400
 
+++ /mnt/buildbot/build/mariadb-10.5.4/mysql-test/suite/perfschema/r/show_aggregate.reject	2020-06-16 23:14:13.568358785 -0400
 
@@ -494,7 +494,7 @@
 
 FROM test.status_results
 
 ORDER BY variable_name;
 
 variable_name	h1	h2	h3	delta	host	Expected
 
-Handler_delete	6	0	0	6	6	OK
 
+Handler_delete	4	0	0	6	4	ERROR
 
 Handler_rollback	6	0	0	6	6	OK
 
 # ================================================================================
 
 # TEST 8: FLUSH STATUS should clear account, host and user status
 
 
 
mysqltest: Result length mismatch

etc.

 Comments   
Comment by Alice Sherepa [ 2020-10-26 ]

recently on 10.5 http://buildbot.askmonty.org/buildbot/builders/kvm-deb-bionic-ppc64le/builds/4934/steps/mtr/logs/stdio

Comment by Alice Sherepa [ 2021-04-12 ]

10.6 51630d595d49c57946d71 http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/19350/steps/test/logs/stdio

perfschema.show_aggregate 'innodb,pot'   w3 [ fail ]
 
        Test ended at 2021-04-09 22:16:11
 
 
 
CURRENT_TEST: perfschema.show_aggregate
 
--- D:/win32-debug/build/src/mysql-test/suite/perfschema/r/show_aggregate.result	2021-04-09 21:53:31.208733200 +0000
 
+++ D:\win32-debug\build\src\mysql-test\suite\perfschema\r\show_aggregate.reject	2021-04-09 22:16:11.438439700 +0000
 
@@ -440,7 +440,7 @@
 
 #
 
 SELECT *, IF (variable_value = 2,'OK','ERROR') AS Expected FROM status_by_user WHERE user IN ('user2') AND variable_name IN ('handler_delete');
 
 USER	VARIABLE_NAME	VARIABLE_VALUE	Expected
 
-user2	Handler_delete	2	OK
 
+user2	Handler_delete	0	ERROR
 
 #
 
 SELECT *, IF (variable_value = 3,'OK','ERROR') AS Expected FROM status_by_user WHERE user IN ('user3') AND variable_name IN ('handler_delete');
 
 USER	VARIABLE_NAME	VARIABLE_VALUE	Expected
 
@@ -464,7 +464,7 @@
 
 #
 
 SELECT *, IF (variable_value = 2,'OK','ERROR') AS Expected FROM status_by_account WHERE user IN ('user2') AND variable_name IN ('handler_delete');
 
 USER	HOST	VARIABLE_NAME	VARIABLE_VALUE	Expected
 
-user2	localhost	Handler_delete	2	OK
 
+user2	localhost	Handler_delete	0	ERROR
 
 #
 
 SELECT *, IF (variable_value = 3,'OK','ERROR') AS Expected FROM status_by_account WHERE user IN ('user3') AND variable_name IN ('handler_delete');
 
 USER	HOST	VARIABLE_NAME	VARIABLE_VALUE	Expected
 
@@ -483,7 +483,7 @@
 
 # ================================================================================
 
 SELECT *, IF (variable_value = 6,'OK','ERROR') AS Expected FROM status_by_host WHERE host IN ('localhost') AND variable_name IN ('handler_delete');
 
 HOST	VARIABLE_NAME	VARIABLE_VALUE	Expected
 
-localhost	Handler_delete	6	OK
 
+localhost	Handler_delete	4	ERROR
 
 #
 
 # STATUS_BY_HOST vs. GLOBAL_STATUS
 
 #
 
 
 
mysqltest: Result length mismatch

Comment by Otto Kekäläinen [ 2023-03-24 ]

Sporadic failure seen in https://launchpadlibrarian.net/657276765/buildlog_ubuntu-lunar-s390x.mariadb_1%3A10.11.2-2~ubuntu23.04.1~1679625322.19956617aa9.dev.otto_BUILDING.txt.gz

perfschema.show_aggregate '1tpc,innodb'  w3 [ fail ]
 
        Test ended at 2023-03-24 03:26:20
 
 
 
CURRENT_TEST: perfschema.show_aggregate
 
--- /<<PKGBUILDDIR>>/mysql-test/suite/perfschema/r/show_aggregate.result	2023-02-01 17:28:03.000000000 +0000
 
+++ /<<PKGBUILDDIR>>/mysql-test/suite/perfschema/r/show_aggregate.reject	2023-03-24 03:26:19.905706995 +0000
 
@@ -500,17 +500,17 @@
 
 SELECT * FROM status_by_account WHERE user IN ('user1', 'user2', 'user3') AND variable_name IN ('handler_delete');
 
 USER	HOST	VARIABLE_NAME	VARIABLE_VALUE
 
 user1	localhost	Handler_delete	0
 
-user2	localhost	Handler_delete	0
 
+user2	localhost	Handler_delete	2
 
 user3	localhost	Handler_delete	0
 
 #
 
 SELECT * FROM status_by_host WHERE host IN ('localhost') AND variable_name IN ('handler_delete');
 
 HOST	VARIABLE_NAME	VARIABLE_VALUE
 
-localhost	Handler_delete	0
 
+localhost	Handler_delete	2
 
 #
 
 SELECT * FROM status_by_user WHERE user IN ('user1', 'user2', 'user3') AND variable_name IN ('handler_delete');
 
 USER	VARIABLE_NAME	VARIABLE_VALUE
 
 user1	Handler_delete	0
 
-user2	Handler_delete	0
 
+user2	Handler_delete	2
 
 user3	Handler_delete	0
 
 # ================================================================================
 
 # CLEANUP
 
 
 
mysqltest: Result content mismatch

Comment by Otto Kekäläinen [ 2023-10-07 ]

I ran extensive tests with 'mtr --big' and did not see this occurring. Logs at https://launchpad.net/~otto/+archive/ubuntu/mariadb/+builds?build_text=&build_state=all.

Generated at Thu Feb 08 09:18:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.