da25960022
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to #106749 and #107300 Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| accessibility | ||
| api_integration | ||
| common | ||
| examples | ||
| functional | ||
| harden | ||
| interpreter_functional | ||
| new_visualize_flow | ||
| package | ||
| plugin_functional | ||
| scripts | ||
| security_functional | ||
| server_integration | ||
| ui_capabilities/newsfeed_err | ||
| visual_regression | ||
| tsconfig.json | ||