| Bug #43716 | Test mysqlbinlog_row_big is failing, needs to be updated | ||
|---|---|---|---|
| Submitted: | 18 Mar 2009 2:22 | Modified: | 6 May 2009 14:47 |
| Reporter: | Patrick Crews | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Server | Severity: | S3 (Non-critical) |
| Version: | 5.1+ | OS: | Any |
| Assigned to: | Patrick Crews | CPU Architecture: | Any |
| Tags: | big test, mysqlbinlog_row_big, test, test_failure | ||
[18 Mar 2009 2:32]
Bugs System
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/69508 2842 Patrick Crews 2009-03-17 Bug#43716: Test mysqlbinlog_row_big is failing, needs to be updated. Altered .test file to re-enable certain disabled portions of the test. Added a master.opt file to set max_allowed_packet Re-recorded .result file to accommodate new changes to the test.
[2 Apr 2009 22:34]
Bugs System
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/71267 2853 Patrick Crews 2009-04-02 Bug#43716: Test mysqlbinlog_row_big is failing, needs to be updated Altered the test to accommodate the new behavior of max_allowed_packet. Had to disconnect / reconnect the default connection for the new value to register. Re-enabled certain parts of the test that were commented out and added some setup / cleanup code to ensure proper reset of max_allowed_packet at the end of the test. Re-recorded the .result file to account for changes to the test.
[5 May 2009 19:39]
Bugs System
Pushed into 5.1.35 (revid:davi.arnaut@sun.com-20090505190206-9xmh7dlc6kom8exp) (version source revid:davi.arnaut@sun.com-20090505190206-9xmh7dlc6kom8exp) (merge vers: 5.1.35) (pib:6)
[6 May 2009 4:11]
Paul DuBois
Test case changes. No changelog entry needed. Setting report to NDI pending push into 6.0.x.
[6 May 2009 14:13]
Bugs System
Pushed into 6.0.12-alpha (revid:svoj@sun.com-20090506125450-yokcmvqf2g7jhujq) (version source revid:patrick.crews@sun.com-20090402223738-gtc4t1hqdb9sahvp) (merge vers: 6.0.11-alpha) (pib:6)
[6 May 2009 14:47]
Paul DuBois
Test case changes. No changelog entry needed.
[15 Jun 2009 8:25]
Bugs System
Pushed into 5.1.35-ndb-6.3.26 (revid:jonas@mysql.com-20090615074202-0r5r2jmi83tww6sf) (version source revid:jonas@mysql.com-20090615070837-9pccutgc7repvb4d) (merge vers: 5.1.35-ndb-6.3.26) (pib:6)
[15 Jun 2009 9:05]
Bugs System
Pushed into 5.1.35-ndb-7.0.7 (revid:jonas@mysql.com-20090615074335-9hcltksp5cu5fucn) (version source revid:jonas@mysql.com-20090615072714-rmfkvrbbipd9r32c) (merge vers: 5.1.35-ndb-7.0.7) (pib:6)
[15 Jun 2009 9:45]
Bugs System
Pushed into 5.1.35-ndb-6.2.19 (revid:jonas@mysql.com-20090615061520-sq7ds4yw299ggugm) (version source revid:jonas@mysql.com-20090615054654-ebgpz7elwu1xj36j) (merge vers: 5.1.35-ndb-6.2.19) (pib:6)
Description: The test mysqlbinlog_row_big is failing and needs to be updated: This is due to changes in the behavior of the variable max_allowed_packet. The session variable is not affected by the set @@global... statement in the test and as a result a domino effect of errors occurs (no data populated to test tables): CURRENT_TEST: main.mysqlbinlog_row_big --- /Users/pcrews/usr/local/bin/data1/work/mysqlbinlog_row_big/mysql-5.1-bugteam/mysql-test/r/mysqlbinlog_row_big.result 2009-03-18 05:13:40.000000000 +0300 +++ /Users/pcrews/usr/local/bin/data1/work/mysqlbinlog_row_big/mysql-5.1-bugteam/mysql-test/r/mysqlbinlog_row_big.reject 2009-03-18 05:16:18.000000000 +0300 @@ -27,32 +27,34 @@ # Insert a big row. # INSERT INTO t1 VALUES (REPEAT('ManyMegaByteBlck', 2097152)); +Warnings: +Warning 1301 Result of repeat() was larger than max_allowed_packet (1048576) - truncated affected rows: 1 How to repeat: Run the test: ./mysql-test-run.pl --force --big mysqlbinlog_row_big Suggested fix: Correct the test. This can be accomplished via a master.opt file to set the max_allowed_packet value at the start of the server or by creating a second connection that will have a value of max_allowed_packet that is affected by the set @@global.max_allowed_packet statement in the test.