Percona XtraBackup moved to https://jira.percona.com/projects/PXB

bug514068_test is failing on innodb51 debug builds when using a randgen test bed

Bug #924517 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Triaged
High
Unassigned

Bug Description

The bug514068 test is failing on debug builds when the server uses a randgen test bed.
I have repeated this test with no test data (as in the original test) and with the sakila database and both pass without incident.

It appears that something is going awry during the prepare phase of things: # do prepare on backup
            cmd = [ innobackupex
                  , "--apply-log"
                  , "--no-timestamp"
                  , "--use-memory=500M"
                  , "--ibbackup=%s" %xtrabackup
                  , backup_path
                  ]
            cmd = " ".join(cmd)
            retcode, output = self.execute_cmd(cmd, output_path, stderr_path, exec_path, True)
            self.assertEqual(retcode, 0,output)

The above assertion fails as innobackupex returns an error code of 255 and no output.
This appears similar to the issue with Bug#924492, as it is also failing during the prepare phase on the same data set.

To repeat:
./kewpie.py bug514068_test against an innodb51_builtin debug build

There is (hacky) code in the test case to allow you to use the sakila database for comparison. comment out all the loading / validation of test data to run without a data set.

Revision history for this message
Patrick Crews (patrick-crews) wrote :

20120130-173117 ===============================================================
20120130-173117 TEST NAME [ RESULT ] TIME (ms)
20120130-173117 ===============================================================
20120130-173117 xtrabackup_main.bug514068_test [ fail ] 38805
20120130-173117 Bug #514068: Output to STDOUT and STDERR is not conventional ... FAIL
20120130-173117 ERROR
<snip>
20120130-173117
20120130-173117 ======================================================================
20120130-173117 FAIL: Bug #514068: Output to STDOUT and STDERR is not conventional
20120130-173117 ----------------------------------------------------------------------
20120130-173117 Traceback (most recent call last):
20120130-173117 File "/home/jenkins/workspace/percona-xtrabackup-trunk-kewpie/BUILD_TYPE/debug/Host/ubuntu-lucid-32bit/xtrabackuptarget/innodb51_builtin/kewpie/percona_tests/xtrabackup_main/bug514068_test.py", line 121, in test_bug514068
20120130-173117 self.assertEqual(retcode, 0,output)
20120130-173117 AssertionError: 255 != 0

summary: bug514068_test is failing on debug builds when server is populated with
- a test bed
+ a randgen test bed
summary: - bug514068_test is failing on debug builds when server is populated with
- a randgen test bed
+ bug514068_test is failing on innodb51 debug builds when using a randgen
+ test bed
Changed in percona-xtrabackup:
status: New → Confirmed
Revision history for this message
Patrick Crews (patrick-crews) wrote :

The test data consists of tables of similar composition. Each table has the same columns, but they are created in randomized order. They are populated with 0,0,1,1,10,10,100,100 rows each.

CREATE TABLE `CC` (
`col_enum_not_null_key` enum ('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z') not null,
`col_bigint_not_null` bigint not null,
`col_enum` enum ('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z'),
`col_char_10_not_null_key` char(10) not null,
`col_char_255_key` char(255),
`col_char_10` char(10),
`col_text_key` text,
`col_bigint_not_null_key` bigint not null,
`col_text_not_null_key` text not null,
`col_char_255_not_null` char(255) not null,
`col_enum_key` enum ('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z'),
`col_char_10_not_null` char(10) not null,
`col_int_key` int,
`col_char_255` char(255),
`col_text_not_null` text not null,
`col_char_255_not_null_key` char(255) not null,
`col_bigint_key` bigint,
pk integer auto_increment,
`col_enum_not_null` enum ('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z') not null,
`col_int_not_null` int not null,
`col_char_10_key` char(10),
`col_bigint` bigint,
`col_int_not_null_key` int not null,
`col_int` int,
`col_text` text,
/*Indices*/
key (`col_enum_not_null_key` ),
key (`col_char_10_not_null_key` ),
key (`col_char_255_key` ),
key (`col_text_key` (255)),
key (`col_bigint_not_null_key` ),
key (`col_text_not_null_key` (255)),
key (`col_enum_key` ),
key (`col_int_key` ),
key (`col_char_255_not_null_key` ),
key (`col_bigint_key` ),
primary key (pk),
key (`col_char_10_key` ),
key (`col_int_not_null_key` )) ;

Revision history for this message
Patrick Crews (patrick-crews) wrote :

Appears to be failing due to indexed text column:
Changing the percona.zz file like this (or by removing 'text' form the types list will allow the test to pass.

=== modified file 'kewpie/randgen/conf/percona/percona.zz'
--- old/kewpie/randgen/conf/percona/percona.zz 2011-10-13 20:38:47 +0000
+++ new/kewpie/randgen/conf/percona/percona.zz 2012-02-01 11:31:39 +0000
@@ -30,7 +30,7 @@ $tables = {

 $fields = {
         types => [ 'bigint' , 'int', 'char(10)', 'char(255)', 'enum' , 'text' ],
- indexes => [undef, 'key' ],
+ indexes => [undef ],
         null => [undef, 'not null' ],
         default => [undef, 'default null' ]
 };

Stewart Smith (stewart)
Changed in percona-xtrabackup:
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Alexey Kopytov (akopytov) wrote :

I'm fairly sure this is a duplicate of bug #924492.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.