-
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
KB-60471: run flaky test in runner only. #61552
KB-60471: run flaky test in runner only. #61552
Conversation
@elasticmachine merge upstream |
💔 Build Failed
Failed CI StepsTest FailuresKibana Pipeline / kibana-xpack-agent / X-Pack API Integration Tests.x-pack/test/api_integration/apis/fleet/agents/acks·ts.apis Fleet Endpoints fleet_agents_acks should return a 200 if this a valid acks requestStandard Out
Stack Trace
Kibana Pipeline / kibana-xpack-agent / X-Pack OpenID Connect API Integration Tests.x-pack/test/oidc_api_integration/apis/authorization_code_flow/oidc_auth·js.apis OpenID Connect authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are providedStandard Out
Stack Trace
History
To update your PR or re-run it, just comment with: |
I investigated a little more and this is issue is happening when the API key start with a
Going to write an issue to fix that |
Cool, I was curious why do we need it to be random. Why not used fixed values for each tests? Seems simpler, except there is a reason why not. |
@nnamdifrankie we need a real ES api key for the tests and I do not think you can generate one with a fixed id, also it's nice that it's random it helped discovering a bug |
Fixed by #61796 |
Summary
Find the cause of the flaky test over static data.
Checklist
Delete any items that are not applicable to this PR.