Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-37439

main.partition_explicit_prune sporadically has `HANDLER_READ_RND_NEXT 5` on arm64

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      While importing 11.8.3 into Debian I saw on arm64 a sporadic value mismatch that went away on a rebuild.

      From https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=arm64&ver=1%3A11.8.3-1&stamp=1755059389&raw=0

      main.partition_explicit_prune            w2 [ fail ]
              Test ended at 2025-08-13 04:22:25
       
      CURRENT_TEST: main.partition_explicit_prune
      --- /build/reproducible-path/mariadb-11.8.3/mysql-test/main/partition_explicit_prune.result	2025-07-28 19:35:03.000000000 +0000
      +++ /build/reproducible-path/mariadb-11.8.3/mysql-test/main/partition_explicit_prune.reject	2025-08-13 04:22:24.495505054 +0000
      @@ -1216,7 +1216,7 @@
       WHERE VARIABLE_NAME LIKE 'HANDLER_%' AND VARIABLE_VALUE > 0;
       VARIABLE_NAME	VARIABLE_VALUE
       HANDLER_COMMIT	1
      -HANDLER_READ_RND_NEXT	3
      +HANDLER_READ_RND_NEXT	5
       HANDLER_TMP_WRITE	24
       # 12 locks (3 in t1, 1 in t3, 2 in t2) x 2 (lock + unlock)
       # 1 read first (first rnd_next in t2)
       
      Result content mismatch
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            otto Otto Kekäläinen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.