Bug #68356 Failed test with MySQL 5.5
Submitted: 13 Feb 2013 8:01 Modified: 7 Mar 2013 13:22
Reporter: Remi Collet Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:1.2.0 OS:Linux (Fedora)
Assigned to: Paulo Jesus CPU Architecture:Any

[13 Feb 2013 8:01] Remi Collet 
Description:
Some tests rely on mysql_config_editor which is only part of MySQL 5.6.

So, running test with MySQL 5.5 fails.

How to repeat:
python check.py

Suggested fix:
I think this tests should be skiped if mysql_config_editor is not available.
[21 Feb 2013 16:38] Paulo Jesus 
Fixed in the next release of MySQL Utilities.

The unit tests for my_print_defaults will be skipped if the mysql_config_editor tool is not accessible.
[5 Mar 2013 13:54] Chuck Bell 
Fixed in release-1.2.1
[7 Mar 2013 6:53] Philip Olson 
Fixed as of MySQL Utilities 1.2.1, and here's the changelog entry:

        The unit tests were corrected to detect if the
        mysql_config_editor is present. If not, unit
        tests that require it are skipped.

Thank you for the bug report.
[7 Mar 2013 13:18] Remi Collet 
The fix doesn't work

======================================================================
ERROR: setUpClass (unit_tests.test_my_print_defaults.TestMyPrintDefaults)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/dev/shm/extras/BUILD/~mysql/mysql-utilities/trunk/unit_tests/test_my_print_defaults.py", line 52, in setUpClass
    "MySQL client tools to your PATH." % str(err))
UtilError: ("MySQL client tools must be accessible to run this tests (('Cannot find location of mysql_config_editor.', 0)). E.g. Add the location of the MySQL client tools to your PATH.", 0)

----------------------------------------------------------------------
Ran 36 tests in 0.010s

FAILED (errors=1)
erreur: Mauvais status de sortie pour /var/tmp/rpm-tmp.WABQlM (%check)
[7 Mar 2013 13:22] Remi Collet 
Sorry for the noise...
And thanks for the fix.