* Set NODE_ENV=production for bin/*
* add tests
* Revert "Set NODE_ENV=production for bin/*"
This reverts commit 8012ed6a2e.
* Revert "Revert "Set NODE_ENV=production for bin/*""
This reverts commit 2fd499c112.
* bump ansible logging verbosity
* upgrade base os
* update base images
* add specificity to docker image glob
* limit memory
* bump base vm memory
* more cpu
* decrease verbosity
* less downloads
* disable shared symlinks
* more logging
* bump concurrency to test stability
* add concurrency group
* revert
* parallelism
* Revert "parallelism"
This reverts commit 4cc00f7144.
There appears to be a brief moment after kibana starts where we are
listening for http connections but immediately closing requests to the
status API. The return code by ansible here is -1, so this adds that as
a valid response to retry.
With a recent virtualbox update, we're getting failures in CI with:
> The IP address configured for the host-only network is not within the
> allowed ranges. Please update the address used to be within the allowed
> ranges and run the command again.
This updates the IP range used to be compatible.
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>
