Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL), 10.4(EOL)
Description
The failure below only happens for me on a Valgrind build (-DCMAKE_BUILD_TYPE=Debug -DWITH_VALGRIND=YES), not on a plain debug or ASAN builds.
On a Valgrind build, it currently happens deterministically, at least on two different machines with different gcc versions.
The test doesn't have to be run with --valgrind, it happens with and without the option alike; it's only the build that matters.
|
10.3 6577a7a8 Valgrind |
$ perl ./mtr main.func_debug --valgrind |
|
|
main.func_debug [ fail ]
|
Test ended at 2020-04-16 21:47:01 |
|
|
CURRENT_TEST: main.func_debug
|
--- /data/bld/10.3-valgrind-nightly/mysql-test/main/func_debug.result 2020-04-16 06:58:36.000000000 +0300
|
+++ /data/bld/10.3-valgrind-nightly/mysql-test/main/func_debug.reject 2020-04-16 21:47:01.119451507 +0300
|
@@ -1671,6 +1671,6 @@
|
2
|
9
|
Warnings:
|
-Note 1105 DBUG: Item_subselect::exec (select max(`test`.`t1`.`a`) from `test`.`t... |
+Note 1105 DBUG: Item_subselect::exec (select max(`test`.`t1`.`a`) from `test`.`t1`) |
DROP TABLE t1; |
SET SESSION debug_dbug="-d,Item_subselect"; |
|
|
mysqltest: Result content mismatch
|
Reproducible on 10.3 and on 10.4 after the recent merge, so it must have been introduced recently. I didn't bisect for the exact commit.
10.2 doesn't have the test.