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

innodb.innodb-page_compression_default failed in buildbot, sporadic

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/5984/steps/test/logs/stdio

      innodb.innodb-page_compression_default 'innodb' w2 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-10-26 23:22:32
      line
      2017-10-26 23:22:31 0 [Warning] InnoDB: Trying to access missing tablespace 594
      

      2017-10-26 23:22:24 0 [Warning] D:/win32-debug/build/sql//Debug/mysqld.exe: unknown option '--loose-pam-debug'
      2017-10-26 23:22:24 0 [Note] Server socket created on IP: '::'.
      2017-10-26 23:22:24 0 [Note] InnoDB: Loading buffer pool(s) from D:\win32-debug\build\mysql-test\var\2\mysqld.1\data\ib_buffer_pool
      2017-10-26 23:22:24 0 [Note] Reading of all Master_info entries succeded
      2017-10-26 23:22:24 0 [Note] Added new Master_info '' to hash table
      2017-10-26 23:22:24 0 [Note] D:/win32-debug/build/sql//Debug/mysqld.exe: ready for connections.
      Version: '10.3.3-MariaDB-debug-log'  socket: ''  port: 16000  Source distribution
      2017-10-26 23:22:25 0 [Note] InnoDB: Buffer pool(s) load completed at 171026 23:22:25
      2017-10-26 23:22:31 0 [Warning] InnoDB: Trying to access missing tablespace 594
      

      Attachments

        Issue Links

          Activity

            alice, does this still occur?
            It is difficult to tell where the access was reported, but MDEV-12173 silenced the warning in the change buffer merge. However, the test does not create any secondary indexes, so change buffer should not cause these messages.

            marko Marko Mäkelä added a comment - alice , does this still occur? It is difficult to tell where the access was reported, but MDEV-12173 silenced the warning in the change buffer merge. However, the test does not create any secondary indexes, so change buffer should not cause these messages.
            alice Alice Sherepa added a comment -

            I can see last time it failed this way - 27-10, recent failures of this test are in 10.1 and 10.3, mostly:

            innodb.innodb-page_compression_default 'innodb' w1 [ fail ]  Found warnings/errors in server log file!
                    Test ended at 2018-04-03 17:20:56
            line
            mysqld: /home/buildbot/buildbot/build/mariadb-10.3.6/sql/sql_list.h:626: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
            Attempting backtrace. You can use the following information to find out
            mysqld: /home/buildbot/buildbot/build/mariadb-10.3.6/sql/sql_list.h:626: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
            ^ Found warnings in /mnt/buildbot/build/mariadb-10.3.6/mysql-test/var/1/log/mysqld.1.err
            

            alice Alice Sherepa added a comment - I can see last time it failed this way - 27-10, recent failures of this test are in 10.1 and 10.3, mostly: innodb.innodb-page_compression_default 'innodb' w1 [ fail ] Found warnings/errors in server log file! Test ended at 2018-04-03 17:20:56 line mysqld: /home/buildbot/buildbot/build/mariadb-10.3.6/sql/sql_list.h:626: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed. Attempting backtrace. You can use the following information to find out mysqld: /home/buildbot/buildbot/build/mariadb-10.3.6/sql/sql_list.h:626: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed. ^ Found warnings in /mnt/buildbot/build/mariadb-10.3.6/mysql-test/var/1/log/mysqld.1.err
            marko Marko Mäkelä added a comment - - edited

            alice, InnoDB does not use sql_list.h. I think that I have seen those assertion failures related to THD object destruction at shutdown, in various tests that shut down the server (MDEV-13644).

            marko Marko Mäkelä added a comment - - edited alice , InnoDB does not use sql_list.h. I think that I have seen those assertion failures related to THD object destruction at shutdown, in various tests that shut down the server ( MDEV-13644 ).

            MDEV-12173 was fixed in InnoDB. MDEV-13644 (not an InnoDB issue) is still open.

            marko Marko Mäkelä added a comment - MDEV-12173 was fixed in InnoDB. MDEV-13644 (not an InnoDB issue) is still open.

            People

              Unassigned Unassigned
              alice Alice Sherepa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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