-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution][Serverless] Logging - Fix explore test issue #195941
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks!
/ci |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
await cloudHandler.deleteSecurityProject(project.id, PROJECT_NAME); | ||
} catch (error) { | ||
// False positive | ||
// eslint-disable-next-line require-atomic-updates | ||
result = error; | ||
failedSpecFilePaths.push(filePath); | ||
log.error(`Something went wrong with the cypress execution: ${error}`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Could we make error message clearer? Something like Cypress runner failed: ${error}
looks better.
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]
History
cc @dkirchan |
Summary
This PR addresses two points:
Copy value
test was moved to the top of the spec file. This allows the proper execution of all the tests. Pending further investigation. Me and @MadameSheema tested this locally and it always passes without any issues.Also I tried to increase the resources of the agent assigned in Buildkite to run the tests but this still does not seem to be resolving the issue.