Andreas Buhr 3d785249ba Restore previous QDateTime behavior in DST gap ... Historic QDateTime behavior when being asked to create a QDateTime in the DST gap was to interpret the given date as if it was in the time before that gap, mapping it to a point in time after the gap. This has changed with a04411119e . Since then, the given date is interpreted as if it was in the time after the gap, thus being mapped to a point in time before the gap. This patch restores the historic behavior. This was not caught by Coin because machines ran in timezone "Atlantic/Reykjavik" which does not have DST since 1967. This patch changes tests to always run in "Europe/Oslo". Driveby: Test function "findSpring" did some operations in local time, even though being asked to work in a specific time zone. Fixed that. Fixes: QTBUG-86960 Fixes: QTBUG-89208 Pick-to: 6.0 5.15 Change-Id: Iecce5898bf9711a10e7dfc0a25e4bbeaed1c8ade Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2020-12-15 15:54:46 +01:00
..
qcalendar	QCalendar: increase coverage by tests	2020-11-27 13:26:52 +01:00
qdate	Android: blacklist a list of failing tests for android	2020-11-04 12:27:49 +02:00
qdatetime	Restore previous QDateTime behavior in DST gap	2020-12-15 15:54:46 +01:00
qdatetimeparser	CMake: Regenerate projects using pro2cmake one last time	2020-12-10 11:52:30 +01:00
qtime	Check time-text is long enough while checking for its colons	2020-10-19 17:44:05 +02:00
qtimezone	Android: blacklist a list of failing tests for android	2020-11-04 12:27:49 +02:00
CMakeLists.txt	Add unit tests for qdatetimeparser	2020-10-23 20:33:18 +02:00
time.pro	Add unit tests for qdatetimeparser	2020-10-23 20:33:18 +02:00