TargetSolver: use simple date arithmetics instead of createDateTimeFromMillis
Maybe this made sense long time ago, but nowadays we are using equivalence testers which tolerate date differences with more flexibility. createDateTimeFromMillis was also problematic as it uses internal private attributes of DateTime which is a pylint error with more recent DateTime
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#389793
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:11:50
|
||||||
passed |
#389779
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:14:11
|
||||||
passed |
#389314
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:12:32
|
||||||
passed |
#389413
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:16:19
|
||||||
passed |
#389302
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:12:14
|
||||||
passed |
#389425
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:25:37
|
||||||