There are two things impacting this:
- this used the current time (fixed)
- this depends on the system timezone database (reference data adapted to latest version of the timezone package)
dfaure |
There are two things impacting this:
No Linters Available |
No Unit Test Coverage |
Buildable 16837 | |
Build 16855: arc lint + arc unit |
It still fails for me.
FAIL! : ICalTimeZonesTest::write() Compared values are not the same Actual (vtimezone) : "BEGIN:VTIMEZONE\r\nTZID:Europe/Prague\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0000\r\nTZOFFSETTO:+0200\r\nDTSTART:19790401T010000\r\nRDATE;VALUE=DATE-TIME:19790401T010000\r\nEND:DAYLIGHT\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+"... Expected (QByteArray(VTZ_Prague)): "BEGIN:VTIMEZONE\r\nTZID:Europe/Prague\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0000\r\nTZOFFSETTO:+0200\r\nDTSTART:19790401T010000\r\nRDATE:19790401T010000\r\nEND:DAYLIGHT\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSET"... Loc: [/d/kde/src/5/frameworks/kcalendarcore/autotests/testicaltimezones.cpp(218)]
RDATE has a different format...