[Reporting] fix functional visualize app test

[tsullivan]

Summary

Unskip functional test. Closes #189590

[tsullivan]

/ci

[tsullivan]

Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6713

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6713

[✅] x-pack/test/functional/apps/visualize/config.ts: 42/42 tests passed.

see run history

[tsullivan]

Seems this test is not flaky after all as it passes in the flaky test runner. However, I don't know why the main issue states there was an error of TypeError: Invalid URL. @mistic can you take a look?

[elasticmachine]

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

[mistic]

@tsullivan cherry-picked your changes into a branch on Kibana repo and run the pipeline on that branch. I'm not sure why but the pipeline still fails with those tests https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/4627#019138df-1849-462e-acec-063307e236aa

I think it's a good idea to open the PR with the unskip in a branch on Kibana repo so we can test more things on the pipeline itself.

At this point I'm not sure what could cause those failres. @jbudz maybe do you have any idea?

[jbudz]

This test is running against a cloud deployment. Did we verify it runs there?

I think it's a good idea to open the PR with the unskip in a branch on Kibana repo so we can test more things on the pipeline itself.

Pipelines can run against pull requests, set the branch to pull/190016/head

[tsullivan]

Pipelines can run against pull requests, set the branch to pull/190016/head

^^ @mistic

[mistic]

@jbudz I had that impression and tried it at https://buildkite.com/elastic/kibana-artifacts-snapshot/builds?branch=pull%2F190016...but now I know why it didn't work..I forgot about the last /head. @tsullivan even better, we can do the testing on that PR itself

For the record, I just started a new build based on the changes on this PR https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/4629

[tsullivan]

@jbudz @mistic I'm not sure there are any action items for me on this. Is there anything I can do to help move this forward?

[jbudz]

This test is running against a cloud deployment. Did we verify it runs there?

I haven't looked at it. Does this need help?

[jbudz]

1. Create cloud deployment
2. Fill in environment variables, excluding TEST_BROWSER_HEADLESS and FORCE_COLOR
3. Run FTR
   

   kibana/.buildkite/scripts/steps/artifacts/cloud.sh

   Lines 75 to 96 in 754595b

   	export TEST_KIBANA_PROTOCOL=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_KIBANA_URL).protocol.replace(':', ''))")
   	export TEST_KIBANA_HOSTNAME=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_KIBANA_URL).hostname)")
   	export TEST_KIBANA_PORT=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_KIBANA_URL).port || 443)")
   	export TEST_KIBANA_USERNAME="$CLOUD_DEPLOYMENT_USERNAME"
   	export TEST_KIBANA_PASSWORD="$CLOUD_DEPLOYMENT_PASSWORD"
   	export TEST_ES_PROTOCOL=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_ELASTICSEARCH_URL).protocol.replace(':', ''))")
   	export TEST_ES_HOSTNAME=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_ELASTICSEARCH_URL).hostname)")
   	export TEST_ES_PORT=$(node -e "console.log(new URL(process.env.CLOUD_DEPLOYMENT_ELASTICSEARCH_URL).port || 443)")
   	export TEST_ES_USERNAME="$CLOUD_DEPLOYMENT_USERNAME"
   	export TEST_ES_PASSWORD="$CLOUD_DEPLOYMENT_PASSWORD"
   	# Enabling ansi color output for Node.js again as we don't need to use it as a script interpreter anymore
   	export FORCE_COLOR=1
   	export TEST_BROWSER_HEADLESS=1
   	# Error: attempted to use the "es" service to fetch Elasticsearch version info but the request failed: ConnectionError: self signed certificate in certificate chain
   	export NODE_TLS_REJECT_UNAUTHORIZED=0
   	echo "--- FTR - Reporting"
   	node --no-warnings scripts/functional_test_runner.js --config x-pack/test/functional/apps/visualize/config.ts --include-tag=smoke --quiet

[tsullivan]

@jbudz @mistic it is still not clear what is actionable for me to do with this PR. Is there something regarding the difference regarding where the test fails?

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 9a3842b

Failed CI Steps

• x-pack/test/alerting_api_integration/security_and_spaces/group1/config.ts
• FTR Configs #41

Test Failures

• [job] [logs] x-pack/test/alerting_api_integration/security_and_spaces/group1/config.ts / alerting api integration security and spaces enabled Alerts - Group 1 alerts backfill rule runs ad hoc backfill task should run all execution sets of a scheduled backfill and correctly generate alerts
• [job] [logs] FTR Configs #41 / Serverless Common UI - Management Index Management Indices can delete index

Metrics [docs]

✅ unchanged

History

• 💚 Build #227153 succeeded 38cc8c3
• 💛 Build #226894 was flaky 978340f
• 💛 Build #226182 was flaky 7b1ab1f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

• Click to trigger kibana-pull-request for this PR!