diff options
| author | Sergey Vojtovich <svoj@mariadb.org> | 2016-06-28 14:53:17 +0400 |
|---|---|---|
| committer | Sergey Vojtovich <svoj@mariadb.org> | 2016-07-08 23:38:05 +0400 |
| commit | ae511cbe387fdc16bf48b4fccc889d6d5d256d76 (patch) | |
| tree | e44fddff98bb9682bb47dcc39621d6e03640d048 /libmysqld/lib_sql.cc | |
| parent | ecb27d2650da546c53bf7ff709cc6bf5bfa7f289 (diff) | |
| download | mariadb-git-ae511cbe387fdc16bf48b4fccc889d6d5d256d76.tar.gz | |
MDEV-9363 - Mroonga tests with datetime field fail on Solaris in buildbot
On Solaris mktime() adds one extra day to tm_mday field and returns appropriate
value for dates 1600-01-01 and earlier. That is 1600-01-01 becomes 1600-01-02.
Solaris mktime manual excerpts:
...
The tm_year member must be for year 1901 or later. Calendar
times before 20:45:52 UTC, December 13, 1901 or after
03:14:07 UTC, January 19, 2038 cannot be represented. Port-
able applications should not try to create dates before
00:00:00 UTC, January 1, 1970 or after 00:00:00 UTC, January
1, 2038.
...
The mktime() function assumes Gregorian dates. Times before
the adoption of the Gregorian calendar will not match his-
torial records.
...
According to manual Mroonga only supports dates and datetimes after 1900:
https://mariadb.com/kb/en/mariadb/about-mroonga/
Technically these tests cover unsupported values and should fail on all
platforms. Disable tests until the problem is fixed upstream.
Diffstat (limited to 'libmysqld/lib_sql.cc')
0 files changed, 0 insertions, 0 deletions