mariadb/storage/mroonga
Sergey Vojtovich ae511cbe38 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.
2016-07-08 23:38:05 +04:00
..
build
data
lib
mysql-test MDEV-9363 - Mroonga tests with datetime field fail on Solaris in buildbot 2016-07-08 23:38:05 +04:00
packages
test
tools
udf
vendor/groonga
appveyor.yml
AUTHORS
autogen.sh
ChangeLog
CMakeLists.txt
config.sh.in
configure.ac
COPYING
gpg_uid
ha_mroonga.cpp Merge branch '10.0' into 10.1 2016-06-28 22:01:55 +02:00
ha_mroonga.def
ha_mroonga.hpp
Makefile.am
mrn_constants.hpp
mrn_err.h
mrn_macro.hpp
mrn_mysql.h
mrn_mysql_compat.h
mrn_table.cpp
mrn_table.hpp
mrn_variables.hpp
mrn_version.h.in
NEWS
plugin_version
README
required_groonga_normalizer_mysql_version
required_groonga_version
sources.am
version
version_in_hex
version_major
version_micro
version_minor

See doc/locale/en/html/index.html or doc/locale/ja/html/index.html