[Security Solution] Cypress test runner doesn't start locally on Intel-based Macs #164435
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Detection Engine
Security Solution Detection Engine Area
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Team:Threat Hunting
Security Solution Threat Hunting Team
technical debt
Improvement of the software architecture and operational architecture
test
Epic: #153633
Related to: #162698 (review)
Summary
If you are on a Macbook with an Intel processor, and you
cd x-pack/test/security_solution_cypress
andyarn cypress:open:ess
, you will see an error and Cypress test runner won't start:yarn cypress:open:serverless
We need to fix the root cause so people don't have to use the workaround (below).
Workaround
@nkhristinin suggested a workaround: run Cypress tests against your local ES and Kibana. You will need to run ES and Kibana separately, and then run only the Cypress test runner pointing to them:
Also, this command didn't work for @nkhristinin until he commented this in
kibana.dev.yaml
:Cause
@rylnd and @nkhristinin got some more data and they have reproducibly (at least on two machines) isolated this issue to a particular commit:
757c881b9a8
. Running FTRs locally before this commit works as expected; afterward they fail.They isolated it to some new transforms being installed/started during o11y's plugin setup:
What appears to be happening is that the transform is being started, does not respond within 30s, and the uncaught error response then crashes kibana.
This doesn't affect CI because of this code:
The text was updated successfully, but these errors were encountered: