calendar: More fixes with exceptions when not repeating
The fixes from !630 were not enough, exceptions set on days were calendar did not repeat were also confusing other exceptions after this. Simplify implementation a lot, instead of keeping track of the next exception date, start by building a set of all exceptions dates and use membership of this set as a criterion to skip exceptions. /reviewed-on !1030
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
running |
#44497
external
|
ERP5.UnitTest-Master |
44315:31:56 |
||||||
running |
#44502
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
44315:30:20 |
||||||
passed |
#44513
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:15:04
|
||||||
failed |
#44475
external
retried
|
ERP5.UnitTest-Master |
01:58:29
|
||||||
passed |
#44410
external
retried
|
ERP5.UnitTest-Master |
|
||||||
passed |
#44457
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:34:26
|
||||||
failed |
#44491
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:32:40
|
||||||
passed |
#44429
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:34:20
|
||||||
passed |
#44448
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:14:00
|
||||||
passed |
#44482
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:15:56
|
||||||
passed |
#44438
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:14:18
|
||||||