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

[test-failed]: X-Pack API Integration Tests1.x-pack/test/api_integration/apis/ml/data_frame_analytics/get·ts - apis Machine Learning data frame analytics GET data_frame/analytics "before all" hook in "GET data_frame/analytics" #68860

Closed
liza-mae opened this issue Jun 11, 2020 · 6 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml test-cloud

Comments

@liza-mae
Copy link
Contributor

Version: 7.8.0
Class: X-Pack API Integration Tests1.x-pack/test/api_integration/apis/ml/data_frame_analytics/get·ts
Stack Trace:
Error: expected 200 "OK", got 400 "Bad Request"
at Test._assertStatus (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/supertest/lib/test.js:268:12)
at Test._assertFunction (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/supertest/lib/test.js:283:11)
at Test.assert (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/supertest/lib/test.js:173:18)
at assert (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/supertest/lib/test.js:131:12)
at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/supertest/lib/test.js:128:5
at Test.Request.callback (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/superagent/lib/node/index.js:718:3)
at parser (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/superagent/lib/node/index.js:906:18)
at Stream.res.on (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/superagent/lib/node/parsers/json.js:19:7)
at Unzip.unzip.on (/var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackExt/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/superagent/lib/node/unzip.js:55:12)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
Platform: cloud
Build Num: 324

@liza-mae liza-mae added failed-test A test failure on a tracked branch, potentially flaky-test test-cloud labels Jun 11, 2020
@elasticmachine
Copy link
Contributor

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

@liza-mae liza-mae added the :ml label Jun 11, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@pheyos pheyos self-assigned this Jun 11, 2020
@pheyos
Copy link
Member

pheyos commented Jun 11, 2020

Similar to #63048, just for the API tests.

@liza-mae
Copy link
Contributor Author

It is best if this test can be rewritten to use 1GB, so we can minimize capacity issues on ESS.

@pheyos
Copy link
Member

pheyos commented Jun 17, 2020

Memory requirements will be reduced with #69295

@pheyos
Copy link
Member

pheyos commented Jun 18, 2020

I've double checked on a manual cloud deployment with 1GB ES, 1GB ML, 1GB Kibana that all ML and Transform tests (API and UI) are passing after the merge of #69295. Closing this issue.

@liza-mae From the ML point of view, we can return to 1GB ML nodes in the cloud cluster, although I'm not sure if there are any solutions tests with ML integration out there that still require more memory.

@pheyos pheyos closed this as completed Jun 18, 2020
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 :ml test-cloud
Projects
None yet
Development

No branches or pull requests

3 participants