[MDEV-15677] perfschema.socket_connect failed in buildbot with wrong result Created: 2018-03-26  Updated: 2018-12-06  Resolved: 2018-12-06

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: 10.4.1, 10.1.38, 10.2.20, 10.3.12

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

Issue Links:
Relates
relates to MDEV-17917 perfschema.socket_connect and main.co... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/7793/steps/test/logs/stdio

perfschema.socket_connect                w4 [ fail ]
        Test ended at 2018-03-24 23:20:14
 
CURRENT_TEST: perfschema.socket_connect
--- D:/winx64-debug/build/src/mysql-test/suite/perfschema/r/socket_connect.result	2018-03-24 22:13:32.563097700 +0000
+++ D:\winx64-debug\build\src\mysql-test\suite\perfschema\r\socket_connect.reject	2018-03-24 23:20:13.431160100 +0000
@@ -173,7 +173,7 @@
   AND OBJECT_INSTANCE_BEGIN <> @default_object_instance_begin
 AND (IP LIKE '%127.0.0.1' OR IP LIKE '%::1');
 Expect 1
-1
+0
 
 # 6.2 Verify that there are no TCP/IP connections in the summary instance table
 
@@ -182,4 +182,4 @@
 WHERE EVENT_NAME LIKE '%client_connection%'
   AND OBJECT_INSTANCE_BEGIN <> @default_object_instance_begin;
 Expect 1
-1
+0
 
mysqltest: Result content mismatch



 Comments   
Comment by Vladislav Vaintroub [ 2018-12-06 ]

fixed in MDEV-17917

Generated at Thu Feb 08 08:23:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.