MySQL Bugs: #37316: Anonymous error messages noticed sometimes, while running tests in MTR

Bug #37316	Anonymous error messages noticed sometimes, while running tests in MTR
Submitted:	10 Jun 2008 18:38	Modified:	17 Jun 2010 22:35
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tests: Server	Severity:	S3 (Non-critical)
Version:	mysql-6.0-backup, mysql-6.0, mysql-5.1-bugteam	OS:	Linux
Assigned to:	Davi Arnaut	CPU Architecture:	Any

Description:
1) Sometimes when I run tests in the mysql test frame work, I get the message as,
Note: net_clear() skipped 362 bytes from file: socket (6)

2) This does not happen every time I run the same test.Not sure why this happens.

How to repeat:
Please find the attached test script and run this script in frame work like
./mysql-test-run.pl backup_online2.test

I get the following after I run the test:
=======================================================

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

main.backup_online1            [ fail ]

Note: net_clear() skipped 362 bytes from file: socket (6)
mysqltest: The specified result file does not exist: '/space/hapr29prefix/mysql-test/r/backup_online1.result'

Thank you for the report.

Verified as described using 6.0 tree.

The test triggers the server to send result/data to the client that it does not expect and thus it's discarded and this print out becomes visible for a server compiled in debug mode.

Noted in 5.1-bugteam as well : 
main.mysqltest                           [ fail ]
        Test ended at 2010-02-23 18:54:54

CURRENT_TEST: main.mysqltest
--- /export/home/pb2/build/sb_0-None-1266925964.53/mysql-5.1-bugteam-gcov/mysql-test/r/mysqltest.result	2010-02-23 14:55:19.000000000 +0300
+++ /export/home/pb2/build/sb_0-None-1266925964.53/mysql-5.1-bugteam-gcov/mysql-test/r/mysqltest.reject	2010-02-23 20:54:54.000000000 +0300
@@ -557,6 +557,7 @@
 f1
 Abcd
 mysqltest: At line 2: Cannot run query on connection between send and reap
+Note: net_clear() skipped 70 bytes from file: socket (6)
 select * from t1;;
 drop table t1;
 mysqltest: At line 1: Missing required argument 'filename' to command 'remove_file'

mysqltest: Result content mismatch

This also happens due to improper usage of mysqltest's commands send and reap. In the attached backup test case, there is plenty wrong usage of the send command.

The particular warning in the mysqltest test case is that, before dying mysqltest violates its own rules and sends a SHOW statement on connection with pending results.

Regarding the case reported in the mysqltest test 2010-02-25: I also noticed this infrequent case and added some filtering to the test to ignore it. This message *may* apparently be printed by mysqltest when it fails while having a pending reap, which is just what it does on purpose here.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/102586

3375 Davi Arnaut	2010-03-08
      Bug#37316: Anonymous error messages noticed sometimes, while running tests in MTR
      
      The problem was that mysqltest could attempt to execute a
      SHOW WARNINGS statement through a connection that was not
      properly reaped, thus violating its own rules.
      
      The solution is to skip SHOW WARNINGS if a connection has
      not been properly repeaed.
     @ client/mysqltest.cc
        Skip SHOW WARNINGS if connection hasn't been reaped.

Good catch, looks like a good enough solution. In theory you might lose some info in very rare cases (perhaps) but that's too marginal to worry about.

Queued to mysql-5.1-bugteam

Pushed into 5.5.4-m3 (revid:alik@sun.com-20100326080914-2pz8ns984e0spu03) (version source revid:alexey.kopytov@sun.com-20100312095153-t4rtoqc7p96lmxvh) (merge vers: 5.5.3-m2) (pib:16)

Pushed into mysql-next-mr (revid:alik@sun.com-20100326081116-m3v4l34yhr43mtsv) (version source revid:alik@sun.com-20100325072612-4sds00ix8ajo1e84) (pib:16)

Pushed into 6.0.14-alpha (revid:alik@sun.com-20100326081944-qja07qklw1p2w7jb) (version source revid:alik@sun.com-20100325073410-4t4i9gu2u1pge7xb) (merge vers: 6.0.14-alpha) (pib:16)

Test suite changes. No changelog entry needed.

Pushed into 5.1.46 (revid:sergey.glukhov@sun.com-20100405111026-7kz1p8qlzglqgfmu) (version source revid:davi.arnaut@sun.com-20100308143020-g5j39bcxv1wh4ads) (merge vers: 5.1.45) (pib:16)

Closed per comment from Paul.

This is happening again.
See: http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2968498

Please, ignore previous comment.
The patch was pushed after the failure I pasted.

Pushed into 5.1.47-ndb-7.0.16 (revid:martin.skold@mysql.com-20100617114014-bva0dy24yyd67697) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Pushed into 5.1.47-ndb-6.2.19 (revid:martin.skold@mysql.com-20100617115448-idrbic6gbki37h1c) (version source revid:martin.skold@mysql.com-20100609211156-tsac5qhw951miwtt) (merge vers: 5.1.46-ndb-6.2.19) (pib:16)

Pushed into 5.1.47-ndb-6.3.35 (revid:martin.skold@mysql.com-20100617114611-61aqbb52j752y116) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)