Skip to content
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

Failing test: Jest Tests.x-pack/plugins/security/public/management/api_keys/api_keys_grid - APIKeysGridPage creates API key with optional expiration, redirects back and displays base64 #97085

Closed
kibanamachine opened this issue Apr 14, 2021 · 5 comments · Fixed by #116991
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort skipped-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! v7.13.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 14, 2021

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 15000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
    at /var/lib/jenkins/workspace/elastic+kibana+master/kibana/x-pack/plugins/security/public/management/api_keys/api_keys_grid/api_keys_grid_page.test.tsx:195:3
    at _dispatchDescribe (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/index.js:30:5)
    at Object.<anonymous> (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/x-pack/plugins/security/public/management/api_keys/api_keys_grid/api_keys_grid_page.test.tsx:73:1)
    at Runtime._execModule (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runtime/build/index.js:746:10)
    at jestAdapter (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at runTestInternal (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 14, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 14, 2021
@mistic mistic added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Apr 14, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 14, 2021
@jportner
Copy link
Contributor

Discussion in this comment thread: #92610 (comment)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger added a commit that referenced this issue Apr 14, 2021
spalger added a commit that referenced this issue Apr 14, 2021
(cherry picked from commit 82b7082)
@spalger
Copy link
Contributor

spalger commented Apr 14, 2021

15 seconds is a very long time for a unit test, I suspect we're either testing too much in a single test or writing integration tests. Unfortunately we don't have great visibility into how often this is failing in PRs (see #97197) but twice in one day on master is more than flaky enough to skip

master/8.0: 82b7082
7.x/7.13: 433e74b

@jportner
Copy link
Contributor

Removing the blocker label as the 7.13.0 release has already passed. This is still in our backlog to work through!

@jportner jportner removed the blocker label Jul 12, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Aug 5, 2021
@XavierM XavierM assigned XavierM and unassigned thomheymann Oct 27, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort skipped-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! v7.13.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants