Details
-
Bug
-
Status: Open (View Workflow)
-
Trivial
-
Resolution: Unresolved
-
10.3, 10.4, 10.5
-
None
Description
CURRENT_TEST: perfschema.socket_connect
|
--- /usr/home/ec2-user/mariadb-server/mysql-test/suite/perfschema/r/socket_connect.result 2022-02-02 01:36:26.000000000 +0000
|
+++ /usr/home/ec2-user/mariadb-server/mysql-test/suite/perfschema/r/socket_connect.reject 2022-02-02 18:11:19.231829000 +0000
|
@@ -1,7 +1,6 @@
|
#==============================================================================
|
# Establish the level of IPV6 support
|
#==============================================================================
|
-connection default;
|
#==============================================================================
|
# Get hostname, port number
|
#==============================================================================
|
 |
mysqltest: Result length mismatch
|
It seems very cosmetic, but I'm wondering if it actually means that execution (e.g. of suite/perfschema/include/socket_ipv6.inc) ends earlier than expected.
Same for perfschema.socket_summary_by_event_name_func.