| Bug #19390 | Test 'rpl_trigger' fails, might be random | ||
|---|---|---|---|
| Submitted: | 27 Apr 2006 0:18 | Modified: | 11 Jan 2008 15:49 |
| Reporter: | Kent Boortz | Email Updates: | |
| Status: | Closed | ||
| Category: | Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.0.21,5.0.36,5.0.37 | OS: | Linux (Red Hat RHAS3 x86 x86_64) |
| Assigned to: | Georgi Kodinov | Target Version: | |
| Triage: | D3 (Medium) | ||
[8 Jun 2006 14:33]
Andrei Elkin
Wrong result is caused by previous tests run, particularly rpl_insert_id that creates, and explicitly call drop function bug15728_insert; the function appeared in the wrong results. I think this bug is fixed by recent change in t/rpl_insert_id.test, ver 1.16, where sync_slave_with_master directive was added to ensure the drop query will be performed on slave.
[7 Mar 2007 10:36]
Daniel Fischer
Re-opening because of similar failure in 5.0.36 and 5.0.37:
rpl_trigger [ fail ]
Errors are (from /PATH/mysqltest-time) :
mysqltest: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/rpl_trigger.result
--- r/rpl_trigger.reject
***************
*** 90,95
--- 90,96
SELECT routine_name, definer
FROM information_schema.routines;
routine_name definer
+ f1 root@localhost
bug12480 root@localhost
SELECT trigger_name, definer
FROM information_schema.triggers;
-------------------------------------------------------
[12 Oct 2007 12:22]
Andrei Elkin
Not to disagree, but this time the failure is of another character. This appearance showed up for the first time here 2007-05-08 18:53:34 mysql-5.0-ndb 41 (tulin@whalegate.ndb.mysql.com-20070508185334) sol10-sparc-a n_stm rpl_trigger [log]
[22 Nov 2007 14:21]
Georgi Kodinov
I've tried 5.0.54 (bk) on my box and on rhas3-x86 with and without --ps-protocol, but wasn't able to get the effect.
[15 Dec 2007 1:21]
Kent Boortz
In the 5.0.54 builds three test runs (so far) show the problem as daniel described it @@ -90,6 +90,7 @@ SELECT routine_name, definer FROM information_schema.routines; routine_name definer +f1 root@localhost bug12480 root@localhost SELECT trigger_name, definer FROM information_schema.triggers; Platforms looks random, and on one platform the test fails in the normal test run, another platform "ps-protocol", and the third "debug". Platforms where Red Hat RHAS3 x86 and x86_64 and Mac OS X 10.3 PowerPC 32-bit.
[17 Dec 2007 16:59]
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/40100 ChangeSet@1.2589, 2007-12-17 18:56:39+02:00, gkodinov@magare.gmz +2 -0 Bug #19390: Test 'rpl_trigger' fails, might be random The checks in the test for bug #12480 were too wide and made the test to depend on the procedures and triggers present in the server. Corrected the test to check only for the procedure and trigger it creates.
[11 Jan 2008 12:18]
Bugs System
Pushed into 6.0.5-alpha
[11 Jan 2008 12:21]
Bugs System
Pushed into 5.1.23-rc
[11 Jan 2008 12:22]
Bugs System
Pushed into 5.0.56
[11 Jan 2008 15:49]
Paul DuBois
Change to test case. No changelog entry needed.
Description: Test 'rpl_trigger' fails, might be random. Failures give a diff like ------------------------------------------------------- *** r/rpl_trigger.result --- r/rpl_trigger.reject *************** *** 103,108 --- 103,110 FROM information_schema.routines; routine_name definer bug12480 root@localhost + bug15728 root@localhost + bug15728_insert root@localhost SELECT trigger_name, definer FROM information_schema.triggers; trigger_name definer ------------------------------------------------------- *** r/rpl_trigger.result --- r/rpl_trigger.reject *************** *** 103,108 --- 103,109 FROM information_schema.routines; routine_name definer bug12480 root@localhost + bug15728_insert root@localhost SELECT trigger_name, definer FROM information_schema.triggers; trigger_name definer How to repeat: Run test case on Red Hat RHAS3 x86 or x86_64