Bug #42541 Intermittent failure of backup_vp_nontx.test fails in PB
Submitted: 2 Feb 2009 11:51 Modified: 10 Feb 2009 21:16
Reporter: Jørgen Løland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version:mysql-6.0-bugteam OS:Any
Assigned to: Jørgen Løland CPU Architecture:Any
Tags: pushbuild, sporadic, test failure

[2 Feb 2009 11:51] Jørgen Løland
Description:
backup.backup_vp_nontx                   [ fail ]
        Test ended at 2009-02-01 22:05:53

CURRENT_TEST: backup.backup_vp_nontx
--- /data0/pushbuild/pb/bzr_mysql-6.0-bugteam/467/bzr_mysql-6.0-bugteam-exp/mysql-test/suite/backup/r/backup_vp_nontx.result	2009-02-01 22:26:48.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-6.0-bugteam/467/bzr_mysql-6.0-bugteam-exp/mysql-test/suite/backup/r/backup_vp_nontx.reject	2009-02-02 00:05:53.000000000 +0300
@@ -80,7 +80,6 @@
 05 Some data to test
 ntx1: 06 Some data to test
 ntx1: Should NOT be in backup
-ntx2: Should NOT be in backup
 con_bup: Dropping the database
 DROP TABLE bup_vp.t1;
 DROP DATABASE bup_vp;

mysqltest: Result content mismatch

 - saving '/dev/shm/var-n_mix-130/log/backup.backup_vp_nontx/' to '/dev/shm/var-n_mix-130/log/backup.backup_vp_nontx/'

Retrying test, attempt(2/3)...

How to repeat:
See PB of mysql-6.0-bugteam

Suggested fix:
This may be caused by a missing reap of the insert done by connection 2 @ line 184.
[2 Feb 2009 16:53] Jørgen Løland
This bug is intermittent, and only happens if the select by chance happens before the insert in connection 2 is scheduled. The suggested fix of reaping the insert will only work if the 'finish_bup' signal is not given until after the reap.
[3 Feb 2009 15:16] Jørgen Løland
A patch for this has already been pushed to mysql-6.0 as part of the merge process (merge mysql-6.0-backup -> mysql-6.0). Thus, it can be fixed in mysql-6.0-bugteam branch by merging with main.
[10 Feb 2009 21:16] Paul DuBois
Test case change. No changelog entry needed.