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

main.udf_query_cache fails on buildbot 11.5+

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.5(EOL), 11.6, 11.7
    • 11.6, 11.7
    • Tests
    • None

    Description

      Very recently (starting in August 2024), main.udf_query_cache has started failing on buildbot in 11.5+. In failures, the value for Qcache_hits seems to go between 1 and 2.

      CURRENT_TEST: main.udf_query_cache
      --- /home/jenkins/workspace/Source-Build-Test/src/mysql-test/main/udf_query_cache.result	2024-08-25 00:29:46.000000000 +0000
      +++ /home/jenkins/workspace/Source-Build-Test/src/mysql-test/main/udf_query_cache.reject	2024-08-25 02:44:41.190204835 +0000
      @@ -9,7 +9,7 @@
       metaphon('MySQL')
       show status like "Qcache_hits";
       Variable_name	Value
      -Qcache_hits	0
      +Qcache_hits	1
       show status like "Qcache_queries_in_cache";
       Variable_name	Value
       Qcache_queries_in_cache	0
      @@ -17,7 +17,7 @@
       metaphon('MySQL')
       show status like "Qcache_hits";
       Variable_name	Value
      -Qcache_hits	0
      +Qcache_hits	1
       show status like "Qcache_queries_in_cache";
       Variable_name	Value
       Qcache_queries_in_cache	0
       
      Result content mismatch
       
       - saving '/dev/shm/var/4/log/main.udf_query_cache/' to '/dev/shm/var/log/main.udf_query_cache/'
       
      Retrying test main.udf_query_cache, attempt(2/2)...
      

      Attachments

        Issue Links

          Activity

            People

              sanja Oleksandr Byelkin
              bnestere Brandon Nesterenko
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.