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

main.symlink-myisam-11902 failed in buildbot with error 40 from storage engine

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 5.5(EOL)
    • N/A
    • Tests, MTR
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/bld-starfs-debug/builds/724/steps/test/logs/stdio

      main.symlink-myisam-11902                w2 [ fail ]
              Test ended at 2018-01-25 02:08:33
       
      CURRENT_TEST: main.symlink-myisam-11902
      mysqltest: At line 54: query 'reap' failed with wrong errno 1030: 'Got error 40 from storage engine', instead of 1017...
       
      The result from queries just before the failure was:
      < snip >
      set debug_sync='now WAIT_FOR ok';
      set debug_sync='now SIGNAL go';
      ERROR HY000: File 'MYSQLTEST_VARDIR/tmp/foo/t1.MYD' not found (Errcode: 40)
      flush tables;
      drop table if exists t1;
      create table t1 (a int, b char(16), index (a))
      index directory="MYSQLTEST_VARDIR/tmp/foo";
      insert t1 values (200, 'some'),(201,'some');
      explain select a from t1;
      id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
      1	SIMPLE	t1	index	NULL	a	5	NULL	2	Using index
      select a from t1;
      a
      200
      201
      flush tables;
      set debug_sync='mi_open_kfile SIGNAL waiting WAIT_FOR run';
      select a from t1;
      set debug_sync='now WAIT_FOR waiting';
      set debug_sync='now SIGNAL run';
       
      More results from queries before failure can be found in /opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/var/2/log/symlink-myisam-11902.log
       
       - skipping '/opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/var/2/log/main.symlink-myisam-11902/'
       
      Retrying test main.symlink-myisam-11902, attempt(2/3)...
      

      main.symlink-aria-11902                  w2 [ fail ]
              Test ended at 2018-01-25 02:08:32
       
      CURRENT_TEST: main.symlink-aria-11902
      mysqltest: In included file "/opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/t/symlink-myisam-11902.test": 
      included from /opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/t/symlink-aria-11902.test at line 6:
      At line 54: query 'reap' failed with wrong errno 1030: 'Got error 40 from storage engine', instead of 1017...
       
      The result from queries just before the failure was:
      < snip >
      set debug_sync='now WAIT_FOR ok';
      set debug_sync='now SIGNAL go';
      ERROR HY000: File 'MYSQLTEST_VARDIR/tmp/foo/t1.MAD' not found (Errcode: 40)
      flush tables;
      drop table if exists t1;
      create table t1 (a int, b char(16), index (a))
      index directory="MYSQLTEST_VARDIR/tmp/foo";
      insert t1 values (200, 'some'),(201,'some');
      explain select a from t1;
      id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
      1	SIMPLE	t1	index	NULL	a	5	NULL	2	Using index
      select a from t1;
      a
      200
      201
      flush tables;
      set debug_sync='mi_open_kfile SIGNAL waiting WAIT_FOR run';
      select a from t1;
      set debug_sync='now WAIT_FOR waiting';
      set debug_sync='now SIGNAL run';
       
      More results from queries before failure can be found in /opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/var/2/log/symlink-aria-11902.log
       
       - skipping '/opt/buildbot-slave/mariadb/starfsmenn1/build/mysql-test/var/2/log/main.symlink-aria-11902/'
       
      Retrying test main.symlink-aria-11902, attempt(2/3)...
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            elenst Elena Stepanova
            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.