> On 26 Mar 2017, at 20:11, Thiago Macieira <[email protected]> wrote: > > This test began failing today: > > FAIL! : tst_QLocale::macDefaultLocale() > 'timeString.contains(expectedGMTSpecifier) || > timeString.contains(expectedGMTSpecifierZeroExtended)' returned FALSE. > (timeString `1:02:03 AM GMT+02:00', expectedGMTSpecifier `GMT+3' or `GMT+03') > > The expectation is correct, since Finland is now in Summer time at GMT+3. > Someone on a Mac, please check why it's getting GMT+02. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development
Hi, Likely a “time propagation” problem. Switzerland changed also in the night of Saturday to Sunday. I have checked that the test failed while I was starting to look into the macOS specific code, midnight passed and then test started to succeed again. I did a quick and rough check using NSCalendar in place of CFGregorianDate and the result was the same, the update to the timezone was only done once march 27 started. Before that, GMT+1 was returned. Samuel
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
