Bug #116390 Test main.opt_hint_resource_group_hypergraph failing testcase check
Submitted: 17 Oct 12:12 Modified: 6 Nov 12:59
Reporter: Laurynas Biveinis (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:9.1.0 OS:MacOS (15.0.1)
Assigned to: CPU Architecture:ARM

[17 Oct 12:12] Laurynas Biveinis
Description:
./mtr main.opt_hint_resource_group_hypergraph
...
[ 50%] main.opt_hint_resource_group_hypergraph   [ fail ]
        Test ended at 2024-10-17 15:11:02

MTR's internal check of the test case 'main.opt_hint_resource_group_hypergraph' failed.
This means that the test case does not preserve the state that existed
before the test case was executed.  Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Results saved in '/Users/laurynas/vilniusdb/mysql-9.1.0/_build-debug/mysql-test/var/tmp/check-mysqld_1.result'.
mysqltest: Logging to '/Users/laurynas/vilniusdb/mysql-9.1.0/_build-debug/mysql-test/var/tmp/check-mysqld_1.log'.
mysqltest: Connecting to server localhost:13000 (socket /tmp/mtr-I4sU/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/check-testcase.test' ...
mysqltest: ... Done processing test commands.
--- /Users/laurynas/vilniusdb/mysql-9.1.0/_build-debug/mysql-test/var/tmp/check-mysqld_1.result	2024-10-17 15:11:02
+++ /Users/laurynas/vilniusdb/mysql-9.1.0/_build-debug/mysql-test/var/tmp/check-mysqld_1.reject	2024-10-17 15:11:02
@@ -779,7 +779,7 @@
 optimizer_max_subgraph_pairs	100000
 optimizer_prune_level	1
 optimizer_search_depth	62
-optimizer_switch	index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,engine_condition_pushdown=on,index_condition_pushdown=on,mrr=on,mrr_cost_based=on,block_nested_loop=on,batched_key_access=off,materialization=on,semijoin=on,loosescan=on,firstmatch=on,duplicateweedout=on,subquery_materialization_cost_based=on,use_index_extensions=on,condition_fanout_filter=on,derived_merge=on,use_invisible_indexes=off,skip_scan=on,hash_join=on,subquery_to_derived=off,prefer_ordering_index=on,hypergraph_optimizer=off,derived_condition_pushdown=on,hash_set_operations=on
+optimizer_switch	index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,engine_condition_pushdown=on,index_condition_pushdown=on,mrr=on,mrr_cost_based=on,block_nested_loop=on,batched_key_access=off,materialization=on,semijoin=on,loosescan=on,firstmatch=on,duplicateweedout=on,subquery_materialization_cost_based=on,use_index_extensions=on,condition_fanout_filter=on,derived_merge=on,use_invisible_indexes=off,skip_scan=on,hash_join=on,subquery_to_derived=off,prefer_ordering_index=on,hypergraph_optimizer=on,derived_condition_pushdown=on,hash_set_operations=on
 optimizer_trace	enabled=off,one_line=off
 optimizer_trace_features	greedy_search=on,range_optimizer=on,dynamic_range=on,repeated_subselect=on
 optimizer_trace_limit	1

mysqltest: Result content mismatch

How to repeat:
See above
[17 Oct 12:58] MySQL Verification Team
Hello Laurynas,

Thank you for the report and feedback!

regards,
Umesh
[6 Nov 12:59] Jon Stephens
Fixed in MySQL 9.2.0.

Testing/HG only--no changelog entry needed.

Closed.