tcph's q2 query leads to crash with enabled QA:


ubuntu@ip-172-31-13-58:~/MariaDBEnterprise/storage/columnstore/columnstore/tests/scripts$ sudo ./run_mtr.sh --record --test_full_name future.query_accelerator
 ・ Adding mtr warnings functions...
patching file mtr_warnings.sql
Hunk #2 succeeded at 269 (offset -2 lines).
/usr/share/mariadb/mariadb-test
MTR Warnings function added
 ・ Test results are RECORDED
 ・ Running suite future with test query_accelerator and --extern=false
Logging: ./mtr  --force --record --max-test-fail=0 --testcase-timeout=60 --suite=columnstore/future query_accelerator
VS config: 
vardir: /usr/share/mariadb/mariadb-test/var
Checking leftover processes...
Removing old var directory...
Creating var directory '/usr/share/mariadb/mariadb-test/var'...
Checking supported features...
MariaDB Version 11.4.9-5-MariaDB-enterprise
 - SSL connections supported
Collecting tests...
Installing system database...

==============================================================================

TEST                                      RESULT   TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[01] Using MTR_BUILD_THREAD 300, with reserved ports 19000..19029
worker[01] mysql-test-run: WARNING: running this script as _root_ will cause some tests to be skipped
columnstore/future.query_accelerator     [ fail ]
        Test ended at 2025-11-12 20:26:09

CURRENT_TEST: columnstore/future.query_accelerator
mysqltest: At line 254: query 'SELECT
l_shipmode,
SUM(CASE WHEN o_orderpriority = '1-URGENT' OR o_orderpriority = '2-HIGH' THEN 1 ELSE 0 END) AS high_line_count,
SUM(CASE WHEN o_orderpriority <> '1-URGENT' AND o_orderpriority <> '2-HIGH' THEN 1 ELSE 0 END) AS low_line_count
FROM orders, lineitem
WHERE o_orderkey = l_orderkey
AND l_shipmode IN ('MAIL', 'SHIP')
AND l_commitdate < l_receiptdate
AND l_shipdate < l_commitdate
AND l_receiptdate >= DATE '1994-01-01'
      AND l_receiptdate < DATE '1995-01-01'
    GROUP BY l_shipmode
ORDER BY l_shipmode' failed: <Unknown> (2013): Lost connection to server during query

The result from queries just before the failure was:
< snip >
883	1004650.68
3627	1004461.04
set columnstore_unstable_optimizer=on;
set optimizer_switch="index_merge=off,index_merge_union=off,index_merge_sort_union=off,index_merge_intersection=off,index_merge_sort_intersection=off,index_condition_pushdown=off,derived_merge=off,derived_with_keys=off,firstmatch=off,loosescan=off,materialization=on,in_to_exists=off,semijoin=off,partial_match_rowid_merge=off,partial_match_table_scan=off,subquery_cache=off,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=off,semijoin_with_cache=off,join_cache_incremental=off,join_cache_hashed=off,join_cache_bka=off,optimize_join_buffer_size=off,table_elimination=off,extended_keys=off,exists_to_in=off,orderby_uses_equalities=off,condition_pushdown_for_derived=on,split_materialized=off,condition_pushdown_for_subquery=off,rowid_filter=off,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=off,cset_narrowing=off,sargable_casefold=off";
SELECT  "QUERY 12";
QUERY 12
QUERY 12
SELECT
l_shipmode,
SUM(CASE WHEN o_orderpriority = '1-URGENT' OR o_orderpriority = '2-HIGH' THEN 1 ELSE 0 END) AS high_line_count,
SUM(CASE WHEN o_orderpriority <> '1-URGENT' AND o_orderpriority <> '2-HIGH' THEN 1 ELSE 0 END) AS low_line_count
FROM orders, lineitem
WHERE o_orderkey = l_orderkey
AND l_shipmode IN ('MAIL', 'SHIP')
AND l_commitdate < l_receiptdate
AND l_shipdate < l_commitdate
AND l_receiptdate >= DATE '1994-01-01'
      AND l_receiptdate < DATE '1995-01-01'
    GROUP BY l_shipmode
ORDER BY l_shipmode;

More results from queries before failure can be found in /usr/share/mariadb/mariadb-test/var/log/query_accelerator.log

 - saving '/usr/share/mariadb/mariadb-test/var/log/columnstore/future.query_accelerator/' to '/usr/share/mariadb/mariadb-test/var/log/future.query_accelerator/'
***Warnings generated in error logs during shutdown after running tests: columnstore/future.query_accelerator

251112 20:26:01 [ERROR] /usr/sbin/mariadbd got signal 11 ;
Attempting backtrace. Include this in the bug report.

--------------------------------------------------------------------------
The servers were restarted 0 times
Spent 0.000 of 51 seconds executing testcases

Completed: Failed 1/1 tests, 0.00% were successful.

Failing test(s): columnstore/future.query_accelerator

The log files in var/log may give you some hint of what went wrong.

If you want to report this error, MariaDB's bug tracker is found at
https://jira.mariadb.org

Errors/warnings were found in logfiles during server shutdown after running the
following sequence(s) of tests:
    columnstore/future.query_accelerator
mysql-test-run: *** ERROR: there were failing test cases
 ・ reports or coredumps:
--- /home/ubuntu/MariaDBEnterprise/storage/columnstore/columnstore/tests/scripts/mtr.future.cores-before	2025-11-12 20:25:18.538416425 +0000
+++ /home/ubuntu/MariaDBEnterprise/storage/columnstore/columnstore/tests/scripts/mtr.future.cores-after	2025-11-12 20:26:11.480661997 +0000
@@ -1,2 +1,3 @@
 core_mariadbd.3660319
 core_mariadbd.3667370
+core_mariadbd.3688378
/tmp
ubuntu@ip-172-31-13-58:~/MariaDBEnterprise/storage/columnstore/columnstore/tests/scripts$