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 Reporting API Integration Tests.x-pack/test/reporting_api_integration/reporting_and_security/network_policy·ts - Reporting APIs Network Policy should fail job when page voilates the network policy #111381

Closed
kibanamachine opened this issue Sep 7, 2021 · 17 comments · Fixed by #134534
Assignees
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. Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Sep 7, 2021

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: expected 500 "Internal Server Error", got 503 "Service Unavailable"
    at Test._assertStatus (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:718:3)
    at IncomingMessage.<anonymous> (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:906:18)
    at endReadableNT (internal/streams/readable.js:1317:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
    at onFailure (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at RetryService.tryForTime (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry.ts:22:12)
    at Context.<anonymous> (test/reporting_api_integration/reporting_and_security/network_policy.ts:38:7)
    at Object.apply (/dev/shm/workspace/parallel/21/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 7, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 7, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 10, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic
Copy link
Member

mistic commented Mar 14, 2022

Skipped.

main: 8d7566b

@tsullivan
Copy link
Member

Latest error message:



└- ✖ fail: Reporting APIs Network Policy should fail job when page voilates the network policy
--
  | │      retry.tryForTime timeout: Error: expected 'Reporting generation failed: ReportingError(code: browser_screenshot_error) "Protocol error (Target.activateTarget): Session closed. Most likely the page has been closed."' to match /Reporting generation failed: ReportingError\(code: browser_unexpectedly_closed_error\) "/



maksimkovalev pushed a commit to maksimkovalev/kibana that referenced this issue Mar 18, 2022
@exalate-issue-sync exalate-issue-sync bot added the impact:critical This issue should be addressed immediately due to a critical level of impact on the product. label Jun 14, 2022
@kibanamachine kibanamachine reopened this Nov 5, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 7.17

@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 5, 2024
@mistic mistic added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Nov 5, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-sharedux (Team:SharedUX)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 5, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - 7.17

@tsullivan
Copy link
Member

Similar error for both recent failures:

  | 2024-11-05 09:47:22 MST | └-: Network Policy
  | 2024-11-05 09:47:22 MST | └-> "before all" hook: beforeTestSuite.trigger for "should fail job when page voilates the network policy"
  | 2024-11-05 09:47:22 MST | └-> "before all" hook for "should fail job when page voilates the network policy"
  | 2024-11-05 09:47:24 MST | └-> should fail job when page voilates the network policy
  | 2024-11-05 09:47:24 MST | └-> "before each" hook: global before each for "should fail job when page voilates the network policy"
  | 2024-11-05 09:47:29 MST | │ERROR [kibana] exitted early: [kibana] exited with code 1
  | 2024-11-05 09:47:29 MST | └- ✖ fail: Reporting APIs Network Policy should fail job when page voilates the network policy
  | 2024-11-05 09:47:29 MST | │      Uncaught Error: Forcing mocha to abort
  | 2024-11-05 09:47:29 MST | │       at Object.next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/run_tests.js:37:25)
  | 2024-11-05 09:47:29 MST | │       at SafeSubscriber.__tryOrUnsub (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:265:10)
  | 2024-11-05 09:47:29 MST | │       at SafeSubscriber.next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:207:14)
  | 2024-11-05 09:47:29 MST | │       at Subscriber._next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:139:22)
  | 2024-11-05 09:47:29 MST | │       at Subscriber.next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:99:12)
  | 2024-11-05 09:47:29 MST | │       at RaceSubscriber.notifyNext (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/observable/race.ts:137:22)
  | 2024-11-05 09:47:29 MST | │       at InnerSubscriber._next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
  | 2024-11-05 09:47:29 MST | │       at InnerSubscriber.Subscriber.next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:99:12)
  | 2024-11-05 09:47:29 MST | │       at TakeSubscriber._next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/operators/take.ts:92:24)
  | 2024-11-05 09:47:29 MST | │       at TakeSubscriber.Subscriber.next (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/Subscriber.ts:99:12)
  | 2024-11-05 09:47:29 MST | │       at EventTarget.handler (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/rxjs/src/internal/observable/fromEvent.ts:201:20)
  | 2024-11-05 09:47:29 MST | │       at EventTarget.[nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20)
  | 2024-11-05 09:47:29 MST | │       at EventTarget.dispatchEvent (node:internal/event_target:755:26)
  | 2024-11-05 09:47:29 MST | │       at abortSignal (node:internal/abort_controller:370:10)
  | 2024-11-05 09:47:29 MST | │       at AbortController.abort (node:internal/abort_controller:392:5)
  | 2024-11-05 09:47:29 MST | │       at onEarlyExit (/opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/@kbn/test/target_node/functional_tests/tasks.js:96:21)
  | 2024-11-05 09:47:29 MST | │       at /opt/local-ssd/buildkite/builds/bk-agent-prod-gcp-1730822499686036503/elastic/kibana-on-merge/kibana/node_modules/@kbn/dev-utils/target_node/proc_runner/proc_runner.js:87:11
  | 2024-11-05 09:47:29 MST | │       at processTicksAndRejections (node:internal/process/task_queues:95:5)
  | 2024-11-05 09:47:29 MST | │
  | 2024-11-05 09:47:29 MST | │

@tsullivan tsullivan self-assigned this Nov 6, 2024
@tsullivan
Copy link
Member

It seems this has not been failing consistently, and is not a skipped test. Closing this.

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:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants