monitor: Remove bootstrap file on failure only
As bootstrapMonitor is run many times and each execution takes taime it's better to have the status file there during monitor is running, especially if previous runs were good. This file is used by other tools to check last state of bootstrap monitor, and if it disappears for execution of monitor it can result with false alarms. /reviewed-on !70
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#37932
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:17:10
|
||||||
failed |
#37941
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:16:36
|
||||||
passed |
#37858
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:14:39
|
||||||
passed |
#37890
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:16:53
|
||||||
failed |
#37873
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:15:49
|
||||||
passed |
#37899
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:16:34
|
||||||