drizzledump test fails on numerous platforms

Bug #393265 reported by Lee Bieber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Stewart Smith

Bug Description

On our x86 OpenSolaris buildbot client the drizzledump test fails most all of the time, there are a few random times when it does pass. If you run a subset of the test or run the test by hand as shown below it passes:

See http://solace.inaugust.com/builders/ubuntu904.32.1

--disable_warnings
DROP TABLE IF EXISTS `t1`;
CREATE TABLE `t1` (
  `a b` INT,
  `c"d` INT,
  `e``f` INT,
  PRIMARY KEY (`a b`, `c"d`, `e``f`)
) ENGINE=MyISAM;
insert into t1 values (0815, 4711, 2006);

--exec $DRIZZLE_DUMP --skip-comments --compatible=ansi --order-by-primary test t1
--exec $DRIZZLE_DUMP --skip-comments --order-by-primary test t1
DROP TABLE `t1`;
--enable_warnings

Test failure result:
------------------------

=======================================================
DEFAULT STORAGE ENGINE: innodb
TEST RESULT TIME (ms)
-------------------------------------------------------

main.drizzledump [ fail ]

drizzledump: Couldn't find table: "non_existing"
--- /export/home/buildbot/drizzle/tests/r/drizzledump.result Sun Jun 28 23:57:23 2009
+++ /export/home/buildbot/drizzle/tests/r/drizzledump.reject Mon Jun 29 01:02:35 2009
@@ -1163,7 +1163,6 @@
 ) ENGINE=MyISAM;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES (815,4711,2006);
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
@@ -1178,7 +1177,6 @@
 ) ENGINE=MyISAM;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES (815,4711,2006);
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

Changed in drizzle:
importance: Undecided → High
milestone: none → aloha
status: New → Confirmed
Changed in drizzle:
assignee: nobody → Stewart Smith (stewart-flamingspork)
Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

Seeing drizzledump fail as of build 1089 on gentoo 64 bit - http://solace.inaugust.com/builders/gentoo.64.1/builds/48/steps/test/logs/stdio

drizzledump: Couldn't find table: "non_existing"
--- ../tests/r/drizzledump.result 2009-06-24 18:50:36.263871478 +0300
+++ ../tests/r/drizzledump.reject 2009-07-07 19:11:25.139179087 +0300
@@ -172,7 +172,7 @@
 ) ENGINE=InnoDB;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES ('` \');
+INSERT INTO `t1` VALUES (0x602010000280100005E71A);
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

drizzletest: Result content mismatch

Stopping All Servers
Restoring snapshot of databases
Resuming Tests

Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

Also failing on SPARC Solaris 10 - http://solace.inaugust.com/builders/solaris10.sparc.1/builds/51/steps/test/logs/stdio

main.drizzledump [ fail ]

drizzledump: Couldn't find table: "non_existing"
--- ../tests/r/drizzledump.result Fri Jul 3 07:55:35 2009
+++ ../tests/r/drizzledump.reject Tue Jul 7 07:13:27 2009
@@ -172,7 +172,7 @@
 ) ENGINE=InnoDB;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES ('` \');
+INSERT INTO `t1` VALUES (0x602010000280100005E71A);
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

drizzletest: Result content mismatch

Stopping All Servers
Restoring snapshot of databases
Resuming Tests

summary: - drizzledump test fails on x86 OpenSolaris
+ drizzledump test fails on OpenSolaris and Gentoo
Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote : Re: drizzledump test fails on OpenSolaris and Gentoo

Also failing on http://gorf.tangent.org/hudson/job/drizzle-inaugust-osx-staging/

main.drizzlecheck [ skipped ] Test requires: 'true'
main.drizzledump [ fail ]

drizzledump: Couldn't find table: "non_existing"
--- ../../tests/r/drizzledump.result 2009-07-06 07:27:23.000000000 +0300
+++ /Users/hudson/src/workspace/drizzle-inaugust-osx-staging/drizzle-2009.07.1089/_build/tests/var/log/drizzledump.reject 2009-07-06 07:31:46.000000000 +0300
@@ -172,7 +172,7 @@
 ) ENGINE=InnoDB;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES ('` \');
+INSERT INTO `t1` VALUES (0x602010000280100005E71A);
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

drizzletest: Result content mismatch

Stopping All Servers
Restoring snapshot of databases
Resuming Tests

summary: - drizzledump test fails on OpenSolaris and Gentoo
+ drizzledump test fails on numerous platforms
Changed in drizzle:
status: Confirmed → Fix Released
Revision history for this message
Joe Daly (skinny.moey) wrote :

I am seeing this on opensuse 11.1 64 bit. The following fails consistently. Im at rev 1128 on the trunk.

main.drizzledump [ fail ] drizzledump: Couldn't find table: "non_existing"
--- /home/jdaly/drizzle/repos/trunk-build/tests/r/drizzledump.result 2009-09-18 19:52:40.000000000 +0300
+++ /home/jdaly/drizzle/repos/trunk-build/tests/r/drizzledump.reject 2009-09-18 20:10:56.000000000 +0300
@@ -172,7 +172,7 @@
 ) ENGINE=InnoDB;

 ALTER TABLE `t1` DISABLE KEYS;
-INSERT INTO `t1` VALUES (0x602010000280100005E71A);
+INSERT INTO `t1` VALUES ('` \');
 ALTER TABLE `t1` ENABLE KEYS;
 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

drizzletest: Result content mismatch

Revision history for this message
Joe Daly (skinny.moey) wrote :

This looks as if it may have been my error, I was picking up a old version of libdrizzle in /usr/lib64 when I deleted this version and made sure I was getting the latest version the drizzledump test ran fine.

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

Other bug subscribers

Remote bug watches

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