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

wsrep* tests fail in buildbot

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-lucid-amd64/builds/4066/steps/test_4/logs/stdio

      wsrep.binlog_format 'innodb_plugin'      w1 [ fail ]
      		 
              Test ended at 2014-11-23 16:56:54
      		 
       
      		 
      CURRENT_TEST: wsrep.binlog_format
      		 
       
      		 
       
      		 
      Failed to start mysqld.1
      		 
      mysqltest failed but provided no output
      		 

      wsrep.pool_of_threads 'innodb_plugin'    w3 [ fail ]
      		 
              Test ended at 2014-11-23 16:57:18
      		 
       
      		 
      CURRENT_TEST: wsrep.pool_of_threads
      		 
       
      		 
       
      		 
      Failed to start mysqld.1
      		 
      mysqltest failed but provided no output
      		 

      wsrep.partition 'innodb_plugin'          w1 [ fail ]
      		 
              Test ended at 2014-11-23 16:57:21
      		 
       
      		 
      CURRENT_TEST: wsrep.partition
      		 
       
      		 
       
      		 
      Failed to start mysqld.1
      		 
      mysqltest failed but provided no output
      		 

      wsrep.grant 'innodb_plugin'              w2 [ fail ]
      		 
              Test ended at 2014-11-23 16:57:21
      		 
       
      		 
      CURRENT_TEST: wsrep.grant
      		 
       
      		 
       
      		 
      Could not execute 'check-testcase' before testcase 'wsrep.grant' (res: 1):
      		 
      mysqltest: Logging to '/dev/shm/var/2/tmp/check-mysqld_1.log'.
      		 
      mysqltest: Results saved in '/dev/shm/var/2/tmp/check-mysqld_1.result'.
      		 
      mysqltest: Connecting to server localhost:16020 (socket /dev/shm/var/tmp/2/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
      		 
      mysqltest: ... Connected.
      		 
      mysqltest: Start processing test commands from './include/check-testcase.test' ...
      		 
      mysqltest: At line 75: Failed to write 55151 bytes to '/dev/shm/var/2/tmp/check-mysqld_1.log', errno: 28
      		 
      not ok
      		 
      mysqltest failed but provided no output

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Task - A task that needs to be done. MDEV-7172 Fix buildbot failures in 10.1 tree

          • Major - Major loss of function.
          • Closed
          links to

          Web Link "SYNC message from member 0 in non-primary configuration. Ignored." warning during concurrent IST #204

          Activity

            Ascending order - Click to sort in descending order
            View 6 older comments
            serg Sergei Golubchik added a comment -

            On the other hand…
            suite/wsrep/suite.pm normally adds scripts and extra to the path. Why does that not happen in your case?

            serg Sergei Golubchik added a comment - On the other hand… suite/wsrep/suite.pm normally adds scripts and extra to the path. Why does that not happen in your case?
            jplindst Jan Lindström (Inactive) added a comment -

            There is some kind of timing problem, it does add those to the path, second run of mtr succeeds but not the first one !

            jplindst Jan Lindström (Inactive) added a comment - There is some kind of timing problem, it does add those to the path, second run of mtr succeeds but not the first one !
            serg Sergei Golubchik added a comment -

            I don't see how that can be timing, the code in suite.pm is very deterministic:

            my ($spath) = grep { -f "$_/wsrep_sst_rsync"; } "$::bindir/scripts", $::path_client_bindir;
            		 
            my ($epath) = grep { -f "$_/my_print_defaults"; } "$::bindir/extra", $::path_client_bindir;
            		 
            $ENV{PATH}="$epath:$ENV{PATH}";
            		 
            $ENV{PATH}="$spath:$ENV{PATH}" unless $epath eq $spath;

            serg Sergei Golubchik added a comment - I don't see how that can be timing, the code in suite.pm is very deterministic: my ($spath) = grep { -f "$_/wsrep_sst_rsync"; } "$::bindir/scripts", $::path_client_bindir; my ($epath) = grep { -f "$_/my_print_defaults"; } "$::bindir/extra", $::path_client_bindir; $ENV{PATH}="$epath:$ENV{PATH}"; $ENV{PATH}="$spath:$ENV{PATH}" unless $epath eq $spath;
            jplindst Jan Lindström (Inactive) added a comment -

            Path has nothing to do with this. We are hitting https://github.com/codership/galera/issues/204

            jplindst Jan Lindström (Inactive) added a comment - Path has nothing to do with this. We are hitting https://github.com/codership/galera/issues/204
            jplindst Jan Lindström (Inactive) added a comment -

            commit b08126aad1a33ec0ad3491b061e888908d1edfe5
            Author: Jan Lindström <jan.lindstrom@skysql.com>
            Date: Thu Feb 5 08:52:17 2015 +0200

            MDEV-7178: wsrep* tests fail in buildbot

            This is temporal test fixt to avoid concurrent IST for now until
            the actual issue https://github.com/codership/galera/issues/204
            is fixed.

            jplindst Jan Lindström (Inactive) added a comment - commit b08126aad1a33ec0ad3491b061e888908d1edfe5 Author: Jan Lindström <jan.lindstrom@skysql.com> Date: Thu Feb 5 08:52:17 2015 +0200 MDEV-7178 : wsrep* tests fail in buildbot This is temporal test fixt to avoid concurrent IST for now until the actual issue https://github.com/codership/galera/issues/204 is fixed.

            People

              jplindst Jan Lindström (Inactive)
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.