Repository navigation
[Reporting] Consolidate startup self-checks - #31931
Conversation
| const page = await browser.newPage(); | ||
| const url = getAbsoluteUrl({ path: API_STATS_ENDPOINT }); | ||
| logger.debug(`Opening page ${url}`); | ||
| await page.goto(url, { waitUntil: 'networkidle0' }); // Look for JSON response |
There was a problem hiding this comment.
Other than the various moving files around and changing a few interfaces, this is the "key" change
There was a problem hiding this comment.
Sweet. I was just thinking it'd be a good idea to expand this test and make sure we can navigate. Glad you beat me to it!
| * or more contributor license agreements. Licensed under the Elastic License; | ||
| * you may not use this file except in compliance with the Elastic License. | ||
| */ | ||
|
|
joelgriffith
left a comment
There was a problem hiding this comment.
Looks great. We should do a follow up issue at some point to remove all the browser type checks since we've deprecated phantom. Not related to this PR, just thinking out loud here.
Yes! There is an existing issue on this: #27136 |
|
retest |
|
Changes in this PR might be causing this failure in CI: |
💔 Build Failed |
|
I think this is slowing down Kibana server startup, and CI is failing due to timeouts |
💔 Build Failed |
|
I'd like to get this in because of the cleanup changes. For now, I removed the part this added that opens a Kibana URL as a self-test check. That part would be nice to have, if it worked. Another plan could be to schedule a one-off task in Task Manager that does this, to be sure we're not fighting for startup resources when we do the self-check. |
💚 Build Succeeded |
* [Reporting] Open test page in reporting browser self-check * comment correction * fix tests * fix test * fix tests more * remove test of open Kibana URL
* [Reporting] Open test page in reporting browser self-check * comment correction * fix tests * fix test * fix tests more * remove test of open Kibana URL
Summary
Edits from investigating #31856
Maintenance/Cleanup:
x-pack/plugins/reporting/server/lib/validate_max_content_length.tsas error catching is handled at a higher level