Bug #16022 Test fails when timestamp is set backwards in binlog (only one platform)
Submitted: 27 Dec 2005 15:59 Modified: 29 Feb 2008 18:27
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.1 and 5.0 OS:Mac OS X (OS X 10.4 (32 bit) only)
Assigned to: Lars Thalmann CPU Architecture:Any

[27 Dec 2005 15:59] Joerg Bruehe
Description:
This symptom is specific to OS X 10.4 (PowerPC), 32 bit, "debug" build.
In this (and only this) combination, it has been found in 4.1.16, 5.0.17, and 5.0.18.

Symptom:
-------------------------------------------------------
*** r/mysqlbinlog2.result
--- r/mysqlbinlog2.reject
***************
*** 657,665
  SET INSERT_ID=5;
  SET TIMESTAMP=1579609946;
  insert into t1 values(null, "e");
- SET INSERT_ID=6;
- SET TIMESTAMP=1579609943;
- insert into t1 values(null, "f");
  # End of log file
  ROLLBACK /* added by mysqlbinlog */;
  /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
--- 657,662
-------------------------------------------------------

How to repeat:
Test suite failure.
[1 Dec 2006 12:46] Joerg Bruehe
I checked all archived build (test) logs of this platform:

Exactly this failure occurs in 4.1.16,        4.1.18, 4.1.19, 4.1.20, 
                          (there is no 4.1.17 log)
5.0.17, 5.0.18, 5.0.19, 5.0.20a, 5.0.21, and 5.0.22;

but starting from 4.1.21 and 5.0.23 all following versions took the test and passed it.

So it seems this got fixed "by accident"
(unless the test was changed, I did not check that).