grid/utils/setRunning: detect the case where pid has been recycled
It can happen that slapos can be terminated without removing the pid file, and another long running process using the same pid from the one in the pid file is running, which cause slapos node to never run. This makes setRunning a little bit clever, by ignoring the process unless it also has `slapos` in its name.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#279963
external
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:56:36
|
||||||
passed |
#279962
external
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
01:30:21
|
||||||
passed |
#279553
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:26:47
|
||||||
failed |
#279794
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:42:31
|
||||||
passed |
#279581
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:22:44
|
||||||
passed |
#279852
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:16:43
|
||||||
failed |
#279647
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:27:23
|
||||||
failed |
#279901
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:37:26
|
||||||
passed |
#279675
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:21:43
|
||||||
passed |
#279691
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
00:21:50
|
||||||
passed |
#279917
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:46:33
|
||||||
passed |
#279585
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:13:15
|
||||||
passed |
#279645
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:23:58
|
||||||
passed |
#279705
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:26:56
|
||||||
passed |
#279810
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:50:19
|
||||||
passed |
#279853
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:48:52
|
||||||
failed |
#279551
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
01:15:20
|
||||||