ERP5TypeFunctionalTestCase: wait a bit longer for Xvfb to start
When running on testnode, runUniTest is responsible for picking a free $DISPLAY. This is implemented by starting Xvfb on a $DISPLAY, waiting a bit and if it is still running we assume the $DISPLAY was free. But it seems sometimes we don't wait enough, when testnodes are overloaded. This implementation is wrong, we could run a command check that X is running, but as explained in the code command below, xdpyinfo or other tools are currently not available in test environment. Since we are considering switching this to seleniumserver (which would take care of running a X Server for us) so this is OK for now.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#123676
external
|
ERP5.CodingStyleTest-Master |
00:58:24
|
||||||
passed |
#123662
external
|
ERP5.PerformanceTest-Master |
00:23:12
|
||||||
failed |
#123675
external
|
ERP5.UnitTest-Master |
01:42:06
|
||||||
failed |
#123681
external
|
ERP5.UnitTest-Master.Medusa |
01:24:14
|
||||||
passed |
#123723
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:24:51
|
||||||
passed |
#123710
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:13:23
|
||||||
passed |
#123669
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:26:16
|
||||||
passed |
#123655
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:11:00
|
||||||