When preparing Jenkinsfile integration, some tests failed if several runs in the same operating environment happened simultaneously. Job had to be marked sequential=1.
Revise if this is still valid, fix whatever is offending (if still valid).
Probable offenders can include hardcoded fixed port numbers, file names (including unix domain sockets, IPC, etc.) or agent names on the stream - so several processes might collide, steal each others responses, etc. unexpectedly for current selftest code.
When preparing Jenkinsfile integration, some tests failed if several runs in the same operating environment happened simultaneously. Job had to be marked
sequential=1.Revise if this is still valid, fix whatever is offending (if still valid).
Probable offenders can include hardcoded fixed port numbers, file names (including unix domain sockets, IPC, etc.) or agent names on the stream - so several processes might collide, steal each others responses, etc. unexpectedly for current selftest code.