MySQL Bugs: #21577: Unusual 'slow_log' warning on Select after downgrading from 5.1->5.0

Bug #21577	Unusual 'slow_log' warning on Select after downgrading from 5.1->5.0
Submitted:	11 Aug 2006 6:15	Modified:	29 Sep 2006 6:33
Reporter:	Erica Moss	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.1.12-beta-log	OS:	Linux (Fedora core 5)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
This problem became evident when using the new upgrade/downgrade test suite with an upgrade from 5.0.22 to 5.1.12-beta-log.  The test in question is the 02-trigger sequence and the failure is encountered during the downgrade phase of the test downgrade02.test.  This test sequence succeeds if the test framework is run using mysqldump to export and import the data during the downgrade, but if it is run as a 'live' downgrade this warning is encountered:

  SELECT * FROM information_schema.triggers WHERE TRIGGER_NAME LIKE 'trg5%';
+ Warnings:
+ Level Warning
+ Code  1017
+ Message       Can't find file: 'slow_log' (errno: 2)

This happens at line 6 of downgrade02.test:
SELECT * FROM information_schema.triggers WHERE TRIGGER_NAME LIKE 'trg5%';

and occurs a number of times after this as well. This warning is not encountered during a minor upgrade test from 5.0.22->5.025 or as mentioned above, when a data export is performed.

How to repeat:
The upgrade/downgrade test framework is found in mysql-test-extra-5.0/mysql-test/suite/updown/bin/
The test files are found in mysql-test-extra-5.0/mysql-test/suite/updown/scenarios/50minor/t
Instructions to configure and run the script are found here:
https://intranet.mysql.com/secure/wiki/QATestInstrucUpDn2

The only real configuration necessary though is to edit the configuration file:
mysql-test-extra-5.0/mysql-test/suite/updown/bin/updown-test-driver.env 
and modify the lines which point to the old version, and the new version

The command to run to reproduce this problem is:
updown-test-driver.sh --up-type=live --down-type=live --test-num=02

When I ran this, both versions were freshly installed.  The 5.0 version is GA, and the 5.1 version was a fresh clone of the tree.

Please paste the output of SHOW VARIABLES LIKE 'have_'; for both trees (5.0 and 5.1)

The results of this are the same in both versions during the initial phase, upgrade phase, and downgrade phase of the test:

mysql> SHOW VARIABLES LIKE 'have_';
Empty set (0.00 sec)

And for SHOW VARIABLES LIKE 'have_%' ?
(sorry for the typo)

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".