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.

Sign up for GitHub

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

Jump to bottom

Failing test: X-Pack Saved Object Tagging API Integration Tests.x-pack/test/saved_object_tagging/api_integration/tagging_api/apis/delete·ts - saved objects tagging API DELETE /api/saved_objects_tagging/tags/{id} should delete the tag #90552

Closed
kibanamachine opened this issue Feb 6, 2021 · 12 comments · Fixed by #90762
Closed

Failing test: X-Pack Saved Object Tagging API Integration Tests.x-pack/test/saved_object_tagging/api_integration/tagging_api/apis/delete·ts - saved objects tagging API DELETE /api/saved_objects_tagging/tags/{id} should delete the tag #90552

kibanamachine opened this issue Feb 6, 2021 · 12 comments · Fixed by #90762
Assignees
@rudolf
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 6, 2021 •
edited
Loading

A test failed on a tracked branch

Error: expected 200 "OK", got 400 "Bad Request"
    at Test._assertStatus (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:718:3)
    at /dev/shm/workspace/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:906:18
    at IncomingMessage.<anonymous> (/dev/shm/workspace/kibana/node_modules/supertest/node_modules/superagent/lib/node/parsers/json.js:19:7)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 6, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mistic mistic added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Feb 7, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

mistic added a commit that referenced this issue Feb 7, 2021
@mistic
skip flaky suite (#90552)
44eff71
mistic added a commit that referenced this issue Feb 7, 2021
@mistic
skip flaky suite (#90552)
8fca529
@mistic
Copy link
Member

mistic commented Feb 7, 2021

Test has been flaky, skipped for now.

master/8.0: 44eff71
7.x/7.12: 8fca529

@rudolf rudolf self-assigned this Feb 8, 2021
gmmorris added a commit to gmmorris/kibana that referenced this issue Feb 8, 2021
@gmmorris
Merge branch 'master' into task-manager/support-limited-concurrency
e3c8430 
* master: (55 commits)
  [APM-UI][E2E] use githubNotify step (elastic#90514)
  [APM] Export ProcessorEvent type (elastic#90540)
  [Lens] Retain column config (elastic#90048)
  [Data Table] Add unit tests (elastic#90173)
  Migrate most plugins to synchronous lifecycle (elastic#89562)
  skip flaky suite (elastic#90555)
  skip flaky suite (elastic#64473)
  [actions] improve email action doc (elastic#90020)
  [Fleet] Support Fleet server system indices (elastic#89372)
  skip flaky suite (elastic#90552)
  Bump immer dependencies (elastic#90267)
  Unrevert "Migrations v2: don't auto-create indices + FTR/esArchiver support (elastic#85778)" (elastic#89992)
  [Search Sessions] Use sync config (elastic#90138)
  chore(NA): add safe guard to remove bazelisk from yarn global at bootstrap (elastic#90538)
  [test] Await retry.waitFor (elastic#90456)
  chore(NA): integrate build buddy with our bazel setup and remote cache for ci (elastic#90116)
  Skip failing suite (elastic#90526)
  [Fleet] Fix incorrect conversion of string to numeric values in agent YAML (elastic#90371)
  [Docs] Update reporting troubleshooting for arm rhel/centos (elastic#90385)
  chore(NA): build bazel projects all at once in the distributable build process (elastic#90328)
  ...
@rudolf rudolf mentioned this issue Feb 9, 2021
Merged
9 tasks
@kibanamachine kibanamachine reopened this Dec 16, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@pgayvallet
Copy link
Contributor

pgayvallet commented Dec 16, 2021 •
edited
Loading

Stacktrace from the additions in #90762:

Trace: {
--
  | statusCode: 400,
  | error: 'Bad Request',
  | message: 'Partial shards failure: search_phase_execution_exception: [query_shard_exception] Reason: failed to create query: [nested] failed to find nested object under path [references]'
  | }

It fails during the second operation (the delete) of the test

const delRes = await supertest.delete(`/api/saved_objects_tagging/tags/tag-1`);

apparently it's when we're trying to find the objects the tag is attached to to remove the reference

@exalate-issue-sync exalate-issue-sync bot added impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:small Small Level of Effort labels Dec 21, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@jbudz
Copy link
Member

jbudz commented Mar 24, 2022

/skip

@pgayvallet
Copy link
Contributor

Tests were re-enabled in #90762, and no failure since #135679, we should probably close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudolf rudolf

Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Re-enable and debug flaky tags test rudolf/kibana
6 participants
@rudolf @pgayvallet @jbudz @mistic @elasticmachine @kibanamachine