Uploaded image for project: 'MariaDB Foundation Development'
  1. MariaDB Foundation Development
  2. MDBF-549

s390x-bbw2-docker-ubuntu-2204 failing all jobs

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • N/A
    • N/A
    • Buildbot
    • None

    Description

      s390x-bbw2-docker-ubuntu-2204

      like MDBI-125 / MDBF-357 for the autobake jobs

      'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.install' -> 'debian/mariadb-plugin-columnstore.install'
      'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postinst' -> 'debian/mariadb-plugin-columnstore.postinst'
      'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postrm' -> 'debian/mariadb-plugin-columnstore.postrm'
      'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.prerm' -> 'debian/mariadb-plugin-columnstore.prerm'
      'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.triggers' -> 'debian/mariadb-plugin-columnstore.triggers'
      Incrementing changelog and starting build scripts
      dch warning: Unable to determine if jammy is a valid Ubuntu release.
      libdistro-info-perl is not installed, Debian release names are not known.
      libdistro-info-perl is not installed, Ubuntu release names are not known.
      Creating package version 1:11.0.1+maria~ubu2204 ... 
      fakeroot: preload library `libfakeroot-sysv.so' not found, aborting.
      program finished with exit code 1
      elapsedTime=3.043898
      

      Test failures on builder s390x-ubuntu-2204 is the same as other s390x workers, which has a problem statement in to MDBF-456 / MDBF-351.

      binlog_encryption.rpl_loaddata_local 'mix' w13 [ retry-fail ]
              Test ended at 2023-03-27 21:22:42
      CURRENT_TEST: binlog_encryption.rpl_loaddata_local
      mysqltest: In included file "./suite/rpl/include/rpl_loaddata_local.inc": 
      included from /home/buildbot/s390x-ubuntu-2204/build/mysql-test/suite/binlog_encryption/rpl_loaddata_local.test at line 2:
      At line 30: query 'select * into outfile '$MYSQLD_DATADIR/rpl_loaddatalocal.select_outfile' from t1' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
      The result from queries just before the failure was:
      include/master-slave.inc
      [connection master]
      create table t1(a int);
      select * into outfile 'MYSQLD_DATADIR/rpl_loaddatalocal.select_outfile' from t1;
       - skipping '/home/buildbot/s390x-ubuntu-2204/build/mysql-test/var/13/log/binlog_encryption.rpl_loaddata_local-mix/'
      Test binlog_encryption.rpl_loaddata_local has failed 2 times, no more retries!
      worker[13] > Restart  - not started
      worker[13] > Restart  - not started
      binlog_encryption.rpl_parallel_rollback_assert 'innodb,row' w5 [ pass ]   3218
      worker[5] > Restart [mysqld.1 - pid: 21640, winpid: 21640] - running with different options '--binlog-format=row --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --log-bin=master-bin' != '--innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --binlog-format=row --log-bin=master-bin'
      worker[5] > Restart [mysqld.2 - pid: 21683, winpid: 21683] - running with different options '--binlog-format=row --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --log-bin=slave-bin' != '--innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --binlog-format=row --log-bin=slave-bin'
      binlog_encryption.encrypted_master 'cbc,innodb,stmt' w14 [ fail ]
              Test ended at 2023-03-27 21:22:44
      CURRENT_TEST: binlog_encryption.encrypted_master
      mysqltest: In included file "/home/buildbot/s390x-ubuntu-2204/build/mysql-test/suite/binlog_encryption/testdata.inc": 
      included from /home/buildbot/s390x-ubuntu-2204/build/mysql-test/suite/binlog_encryption/encrypted_master.test at line 65:
      At line 169: query 'CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt)' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
      The result from queries just before the failure was:
      < snip >
      WHILE counter_name_to_encrypt<12 DO
      SELECT COUNT(*) INTO @cnt FROM innodb_table_name_to_encrypt;
      INSERT INTO innodb_table_name_to_encrypt 
      SELECT int_column_name_to_encrypt+@cnt, NOW(6), blob_column_name_to_encrypt, NULL, NULL
      FROM innodb_table_name_to_encrypt
      ORDER BY int_column_name_to_encrypt;
      SET counter_name_to_encrypt = counter_name_to_encrypt+1;
      END WHILE;
      COMMIT;
      END
      $$
      INSERT INTO myisam_table_name_to_encrypt
      SELECT NULL, 'char_literal_to_encrypt', NULL, 'text_to_encrypt';
      INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
      SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
      INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
      SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
      INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
      SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
      CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt);
      More results from queries before failure can be found in /home/buildbot/s390x-ubuntu-2204/build/mysql-test/var/14/log/encrypted_master.log
       - skipping '/home/buildbot/s390x-ubuntu-2204/build/mysql-test/var/14/log/binlog_encryption.encrypted_master-cbc,innodb,stmt/'
      Too many tests(20) failed! Terminating...
      Only  850  of 6392 completed.
      --------------------------------------------------------------------------
      The servers were restarted 37 times
      Spent 95.685 of 37 seconds executing testcases
      Too many failed: Failed 33/53 tests, 37.74% were successful.
      Failing test(s): binlog_encryption.encrypted_slave binlog_encryption.rpl_special_charset binlog_encryption.encrypted_master binlog_encryption.rpl_loaddata_local binlog_encryption.rpl_loadfile binlog_encryption.rpl_stm_relay_ign_space
      The log files in var/log may give you some hint of what went wrong.
      If you want to report this error, please read first the documentation
      at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html
      Errors/warnings were found in logfiles during server shutdown after running the
      following sequence(s) of tests:
          binlog_encryption.encrypted_slave
          binlog_encryption.rpl_special_charset
          binlog_encryption.encrypted_slave
          binlog_encryption.rpl_special_charset
          binlog_encryption.encrypted_slave
          binlog_encryption.encrypted_slave
          binlog_encryption.rpl_special_charset
          binlog_encryption.rpl_special_charset
          binlog_encryption.rpl_special_charset
          binlog_encryption.encrypted_master
      716 tests were skipped, 0 by the test itself.
      mysql-test-run: *** ERROR: there were failing test cases
      program finished with exit code 1
      elapsedTime=36.974137
      

      Attachments

        Activity

          People

            vladbogo Vlad Bogolin
            danblack Daniel Black
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: