Bug #32683 | Test ps_8falcon fails in 6.0 | ||
---|---|---|---|
Submitted: | 23 Nov 2007 20:49 | Modified: | 28 Nov 2007 21:34 |
Reporter: | Mats Kindahl | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
Version: | 6.0.4-bk | OS: | Any |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
[23 Nov 2007 20:49]
Mats Kindahl
[25 Nov 2007 7:19]
Sveta Smirnova
Thank you for the report. Verified as described.
[27 Nov 2007 15:56]
Kevin Lewis
There was a recent change in suite/falcon/r/ps_8falcon.result that came to the falcon tree with a recent merge. This change, made by Sergey "Gluh" Glukhov <gluh@mysql.com>, seems to have fixed the problem. At least, the Falcon tree does not exhibit this failure. It did not before the merge either, so the change in results must have been from a server change. Sergey, Can you add any comments to this? What server change caused different results? Can you change this to the appropriate category, Lead, reviewers, etc?
[27 Nov 2007 16:15]
Sergei Glukhov
This change comes from Bug#30081 Can't distinguish between auto-set TIMESTAMP and auto-updated TIMESTAMP (see http://lists.mysql.com/commits/37644)
[28 Nov 2007 9:15]
Sergei Glukhov
The fix is here: http://lists.mysql.com/commits/37836
[28 Nov 2007 9:15]
Sergei Glukhov
Pushed into 6.0.4-alpha
[28 Nov 2007 21:34]
Paul DuBois
Test case changes. No changelog entry needed.