Bug#1029164: mariadb: FTBFS on mipsel, mips64el: builds, but test suite in main.order_by_innodb 'innodb' mismatches ('ref' instead of 'range')

Source: mariadb
Version: 1:10.11.1-1
Tags: upstream, confirmed, ftbfs
User: [email protected]
Usertags: mipsel, mips64el
X-Debbugs-CC: [email protected]

After upload of MariaDB 11.10 to Debian (this is a regression from
10.6) the following test started to fail:

main.order_by_innodb 'innodb'            w2 [ fail ]
        Test ended at 2023-01-16 18:25:43

CURRENT_TEST: main.order_by_innodb
--- /<<PKGBUILDDIR>>/mysql-test/main/order_by_innodb.result 2022-11-14
18:10:21.000000000 +0000
+++ /<<PKGBUILDDIR>>/mysql-test/main/order_by_innodb.reject 2023-01-16
18:25:42.932126514 +0000
@@ -250,7 +250,7 @@
 id select_type table type possible_keys key key_len ref rows Extra
 1 PRIMARY t1 index NULL PRIMARY 4 NULL # Using index
 1 PRIMARY t2 eq_ref PRIMARY,id2 PRIMARY 4 func # Using where
-2 DEPENDENT SUBQUERY dd range id2,for_latest_sort for_latest_sort 6
NULL # Using where
+2 DEPENDENT SUBQUERY dd ref id2,for_latest_sort id2 4 test.t1.id #
Using where; Using filesort
 drop table t1,t2,t3;
 # End of 10.2 tests


Merge requests welcome!

https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian