opensolaris-64-test-only is failing drizzledump and mysqldump-max due to unknown diff cause

Bug #583594 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
New
Undecided
Unassigned

Bug Description

These tests are failing due to diff's between expected and actual output that is not readily visible.

The failing output is often in the middle of similar output, so no ready explanation is to be had (like differing EOL characters as I have seen on Windows tests failing, but then again that was Windows <g>).

Interestingly enough, the failing output is often *just* the drizzledump output for a single table - t2 out of 6 tables (t1 and t3 were fine) for mysqldump-max and t1 for drizzledump (t2 following is just fine)

Example output:
main.mysqldump-max [ fail ]
--- .././tests/r/mysqldump-max.result 2010-05-20 22:32:09.647106965 +0300
+++ .././tests/r/mysqldump-max.reject 2010-05-20 22:46:21.535853350 +0300
@@ -79,15 +79,6 @@
 ALTER TABLE `t1` DISABLE KEYS;
 INSERT IGNORE INTO `t1` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
 ALTER TABLE `t1` ENABLE KEYS;
-DROP TABLE IF EXISTS `t2`;
-CREATE TABLE `t2` (
- `id` int DEFAULT NULL,
- `name` varchar(32) DEFAULT NULL
-) ENGINE=ARCHIVE;
-
-ALTER TABLE `t2` DISABLE KEYS;
-INSERT IGNORE INTO `t2` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
-ALTER TABLE `t2` ENABLE KEYS;
 DROP TABLE IF EXISTS `t6`;
 CREATE TABLE `t6` (
   `id` int DEFAULT NULL,
@@ -97,6 +88,15 @@
 ALTER TABLE `t6` DISABLE KEYS;
 INSERT IGNORE INTO `t6` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
 ALTER TABLE `t6` ENABLE KEYS;
+DROP TABLE IF EXISTS `t2`;
+CREATE TABLE `t2` (
+ `id` int DEFAULT NULL,
+ `name` varchar(32) DEFAULT NULL
+) ENGINE=ARCHIVE;
+
+ALTER TABLE `t2` DISABLE KEYS;
+INSERT IGNORE INTO `t2` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
+ALTER TABLE `t2` ENABLE KEYS;

Will need to investigate further as I am currently stumped for what is happening.

Related branches

Revision history for this message
Monty Taylor (mordred) wrote : Re: [Bug 583594] [NEW] opensolaris-64-test-only is failing drizzledump and mysqldump-max due to unknown diff cause

It's ordering again ... check it - table t2 has moved to below table t6
in this.

On 05/20/2010 04:27 PM, Patrick Crews wrote:
> Public bug reported:
>
> These tests are failing due to diff's between expected and actual output
> that is not readily visible.
>
> The failing output is often in the middle of similar output, so no ready
> explanation is to be had (like differing EOL characters as I have seen
> on Windows tests failing, but then again that was Windows <g>).
>
> Interestingly enough, the failing output is often *just* the drizzledump
> output for a single table - t2 out of 6 tables (t1 and t3 were fine) for
> mysqldump-max and t1 for drizzledump (t2 following is just fine)
>
> Example output:
> main.mysqldump-max [ fail ]
> --- .././tests/r/mysqldump-max.result 2010-05-20 22:32:09.647106965 +0300
> +++ .././tests/r/mysqldump-max.reject 2010-05-20 22:46:21.535853350 +0300
> @@ -79,15 +79,6 @@
> ALTER TABLE `t1` DISABLE KEYS;
> INSERT IGNORE INTO `t1` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
> ALTER TABLE `t1` ENABLE KEYS;
> -DROP TABLE IF EXISTS `t2`;
> -CREATE TABLE `t2` (
> - `id` int DEFAULT NULL,
> - `name` varchar(32) DEFAULT NULL
> -) ENGINE=ARCHIVE;
> -
> -ALTER TABLE `t2` DISABLE KEYS;
> -INSERT IGNORE INTO `t2` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
> -ALTER TABLE `t2` ENABLE KEYS;
> DROP TABLE IF EXISTS `t6`;
> CREATE TABLE `t6` (
> `id` int DEFAULT NULL,
> @@ -97,6 +88,15 @@
> ALTER TABLE `t6` DISABLE KEYS;
> INSERT IGNORE INTO `t6` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
> ALTER TABLE `t6` ENABLE KEYS;
> +DROP TABLE IF EXISTS `t2`;
> +CREATE TABLE `t2` (
> + `id` int DEFAULT NULL,
> + `name` varchar(32) DEFAULT NULL
> +) ENGINE=ARCHIVE;
> +
> +ALTER TABLE `t2` DISABLE KEYS;
> +INSERT IGNORE INTO `t2` VALUES (1,'first value'),(2,'first value'),(3,'first value'),(4,'first value'),(5,'first value');
> +ALTER TABLE `t2` ENABLE KEYS;
>
> Will need to investigate further as I am currently stumped for what is
> happening.
>
> ** Affects: drizzle
> Importance: Undecided
> Status: New
>

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

ACK. I'll update the ordering bug and close this out. Thanks for seeing this - it's always good to have extra eyes on bugs : )

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.