synchronizeDynamicModules: Flush ZODB cache.
Should fix most of the cases where reloading components cause breakage. There is still a race condition between a transaction's cache being actually flushed (which can only happen at transaction boundaries) and another transaction doing the actual class reload, which will immediately affect all the started transactions in the same process.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#113459
external
|
ERP5.CodingStyleTest-Master |
00:45:19
|
||||||
passed |
#113458
external
|
ERP5.PerformanceTest-Master |
00:30:59
|
||||||
failed |
#113514
external
|
ERP5.UnitTest-Master |
01:53:25
|
||||||
failed |
#113482
external
|
ERP5.UnitTest-Master.Medusa |
01:10:28
|
||||||
passed |
#113519
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:17:57
|
||||||
passed |
#113508
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:09:53
|
||||||
failed |
#113481
external
retried
|
ERP5.UnitTest-Master |
01:05:19
|
||||||
passed |
#113442
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:21:48
|
||||||
passed |
#113475
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:13:37
|
||||||
passed |
#113452
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:17:32
|
||||||