Bug #77948 mysqldbcompare and mysqldiff fails to compare two server.
Submitted: 5 Aug 2015 12:56 Modified: 7 Sep 2015 6:22
Reporter: Prayag Dave Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Utilities Severity:S2 (Serious)
Version:MySql utilities 1.5.4 OS:Windows
Assigned to: CPU Architecture:Any

[5 Aug 2015 12:56] Prayag Dave

When i compare two database, mysqluc stucks in halfway and it shows error as following:

Traceback (most recent call last):
  File "G:\ade\build\sb_0-14553893-1424966082.93\Python-2.7.6-windows-x86-32bit\
lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
  File "scripts\mysqldiff.py", line 245, in <module>
  File ".\mysql\utilities\command\diff.py", line 149, in database_diff
  File ".\mysql\utilities\command\diff.py", line 92, in object_diff
  File ".\mysql\utilities\common\dbcompare.py", line 646, in diff_objects
  File ".\mysql\utilities\common\dbcompare.py", line 466, in _check_tables_struc
  File ".\mysql\utilities\common\database.py", line 1206, in get_object_definiti
  File ".\mysql\utilities\common\server.py", line 1263, in exec_query
  File ".\mysql\connector\cursor.py", line 339, in close
mysql.connector.errors.InternalError: Unread result found.

How to repeat:
I have tried with both mysqldiff and mysqldbcompare command. 

mysqldiff --server1=username:password@hostname:3307 --server2=username:pasword@localhost:3306 DB1:DB1 --force --difftype=sql --changes-for=server2

mysqldbcompare --server1=username:password@hostname:3307 --server2=username:pasword@localhost:3306 DB1:DB1 --run-all-test --difftype=sql changes-for=server2

it gets stuck on both on both command.
[7 Aug 2015 6:22] MySQL Verification Team
Hi Prayag,

Thank you for the report.
Could you please provide repeatable test case(exact schema and if you prefer then upload as private) to reproduce this issue at our end?If you can provide more information, feel free to add it to this bug and change the status back  to 'Open'.

Thank you for your interest in MySQL.

[7 Aug 2015 6:22] MySQL Verification Team
Also, see Bug #73841
[8 Sep 2015 1:00] Bugs System
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".