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 Reporting API Integration Tests.x-pack/test/reporting_api_integration/reporting_and_security/validation·ts - Reporting APIs Job parameter validation printablePdfV2 fails if there is an invalid layout ID #143738

Closed
kibanamachine opened this issue Oct 20, 2022 · 6 comments · Fixed by #143873
Closed

Failing test: X-Pack Reporting API Integration Tests.x-pack/test/reporting_api_integration/reporting_and_security/validation·ts - Reporting APIs Job parameter validation printablePdfV2 fails if there is an invalid layout ID #143738

kibanamachine opened this issue Oct 20, 2022 · 6 comments · Fixed by #143873
Assignees
@tsullivan
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead failed-test A test failure on a tracked branch, potentially flaky-test impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 20, 2022 •
edited
Loading

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: expected 404 to equal 500
    at Assertion.assert (node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.equal (node_modules/@kbn/expect/expect.js:227:8)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-3d929e060032894f/elastic/kibana-on-merge/kibana/x-pack/test/reporting_api_integration/reporting_and_security/validation.ts:83:35
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runAttempt (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:33:15)
    at retryForSuccess (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:71:21)
    at RetryService.tryForTime (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry.js:33:12)
    at Context.<anonymous> (x-pack/test/reporting_api_integration/reporting_and_security/validation.ts:77:9)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-3d929e060032894f/elastic/kibana-on-merge/kibana/node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:22:9
    at retryForSuccess (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:61:13)
    at RetryService.tryForTime (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry.js:33:12)
    at Context.<anonymous> (x-pack/test/reporting_api_integration/reporting_and_security/validation.ts:77:9)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 20, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 20, 2022
@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 Oct 20, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.5

@elasticmachine
Copy link
Contributor

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

@tsullivan tsullivan self-assigned this Oct 24, 2022
@petrklapka petrklapka added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) and removed Team:AppServicesUx labels Oct 24, 2022
@tsullivan tsullivan mentioned this issue Oct 26, 2022
Merged
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort labels Oct 26, 2022
@kibanamachine kibanamachine reopened this Mar 18, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@tsullivan
Copy link
Member

Failure is happening because timeout is not long enough:

2024-03-18 15:28:17 MST	       └-> fails if there is an invalid layout ID
2024-03-18 15:28:17 MST	         └-> "before each" hook: global before each for "fails if there is an invalid layout ID"
2024-03-18 15:28:36 MST	         └- ✖ fail: Reporting APIs Job parameter validation printablePdfV2 fails if there is an invalid layout ID
2024-03-18 15:28:36 MST	         │      Error: retry.tryForTime timeout: Error: expected 503 to equal 500
2024-03-18 15:28:36 MST	         │     at Assertion.assert (expect.js:100:11)
2024-03-18 15:28:36 MST	         │     at Assertion.equal (expect.js:227:8)
2024-03-18 15:28:36 MST	         │     at validation.ts:83:35
2024-03-18 15:28:36 MST	         │     at processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-03-18 15:28:36 MST	         │     at runAttempt (retry_for_success.ts:29:15)
2024-03-18 15:28:36 MST	         │     at retryForSuccess (retry_for_success.ts:79:21)
2024-03-18 15:28:36 MST	         │     at RetryService.tryForTime (retry.ts:23:12)
2024-03-18 15:28:36 MST	         │     at Context.<anonymous> (validation.ts:77:9)
2024-03-18 15:28:36 MST	         │     at Object.apply (wrap_function.js:73:16)
2024-03-18 15:28:36 MST	         │       at onFailure (retry_for_success.ts:17:9)
2024-03-18 15:28:36 MST	         │       at retryForSuccess (retry_for_success.ts:67:13)
2024-03-18 15:28:36 MST	         │       at RetryService.tryForTime (retry.ts:23:12)
2024-03-18 15:28:36 MST	         │       at Context.<anonymous> (validation.ts:77:9)
2024-03-18 15:28:36 MST	         │       at Object.apply (wrap_function.js:73:16)

@tsullivan
Copy link
Member

I've been keeping an eye on this to see if more failures occur, and they haven't. Therefore I'm choosing not to update the timeout in the test, for now.

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

@tsullivan tsullivan

Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead failed-test A test failure on a tracked branch, potentially flaky-test impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Milestone
No milestone
4 participants
@tsullivan @elasticmachine @kibanamachine @petrklapka