Bug #104429 | MTR uses wrong timezone | ||
---|---|---|---|
Submitted: | 27 Jul 2021 14:55 | Modified: | 25 Aug 2021 8:36 |
Reporter: | Satya Bodapati (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Tools: MTR / mysql-test-run | Severity: | S3 (Non-critical) |
Version: | 5.7.X, 8.0.X, 5.7.35, 8.0.26 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[27 Jul 2021 14:55]
Satya Bodapati
[27 Jul 2021 15:39]
MySQL Verification Team
Hello Satya, Thank you for the report and feedback. regards, Umesh
[18 Aug 2021 16:23]
Bjørn Munch
MTR unfortunately needs to hardcode a particular timezone in order to get consistent output from any queries that would include the current time in some form. So this code is necessary. I tested changing it to something else in the lines you quoted and that caused 45 tests in the main suite (of 8.0) to fail due to result mismatch. The same would be expected if the timezone wasn't hardcoded. There are historical reasons why Finnish DST was chosen rather than UTC.
[25 Aug 2021 8:36]
Satya Bodapati
Bjorn, There is some logic in MTR to skip the hardcoded timezone settings based on mysqld parameters passed. Currently that logic doesn't recognize this parameter. It has two or three hardcoded options.