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: X-Pack Spaces API Integration Tests -- security_and_spaces.x-pack/test/spaces_api_integration/security_and_spaces/apis/copy_to_space·ts - spaces api with security copy to spaces rbac user with all globally from the space_1 space should return 200 when copying to multiple spaces #54106

Closed
kibanamachine opened this issue Jan 7, 2020 · 6 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 7, 2020

A test failed on a tracked branch

{ Error: expected { doc_count_error_upper_bound: 0,
  sum_other_doc_count: 0,
  buckets: 
   [ { key: 'dashboard', doc_count: 2 },
     { key: 'index-pattern', doc_count: 1 },
     { key: 'maps-telemetry', doc_count: 1 },
     { key: 'visualization', doc_count: 5 } ] } to sort of equal { doc_count_error_upper_bound: 0,
  sum_other_doc_count: 0,
  buckets: 
   [ { key: 'dashboard', doc_count: 2 },
     { key: 'index-pattern', doc_count: 1 },
     { key: 'visualization', doc_count: 5 } ] }
    at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
    at assertSpaceCounts (test/spaces_api_integration/common/suites/copy_to_space.ts:156:28)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  actual:
   '{\n  "buckets": [\n    {\n      "doc_count": 2\n      "key": "dashboard"\n    }\n    {\n      "doc_count": 1\n      "key": "index-pattern"\n    }\n    {\n      "doc_count": 1\n      "key": "maps-telemetry"\n    }\n    {\n      "doc_count": 5\n      "key": "visualization"\n    }\n  ]\n  "doc_count_error_upper_bound": 0\n  "sum_other_doc_count": 0\n}',
  expected:
   '{\n  "buckets": [\n    {\n      "doc_count": 2\n      "key": "dashboard"\n    }\n    {\n      "doc_count": 1\n      "key": "index-pattern"\n    }\n    {\n      "doc_count": 5\n      "key": "visualization"\n    }\n  ]\n  "doc_count_error_upper_bound": 0\n  "sum_other_doc_count": 0\n}',
  showDiff: true }

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 7, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@legrego
Copy link
Member

legrego commented Jan 10, 2020

Reclosing; Let's see if that was a stale run which caused this to reopen

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@legrego legrego removed their assignment Jul 28, 2021
@legrego legrego added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Jul 28, 2021
@elasticmachine
Copy link
Contributor

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

@jportner
Copy link
Contributor

The Jenkins build is over a year old, and the original query / test assertion that allowed this to fail has been updated. Since this has not failed in ~18 months, I think it's safe to close this issue. Will investigate if it reopens with a fresh build.

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 Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

4 participants