paul-rogers opened a new issue, #13115: URL: https://github.com/apache/druid/issues/13115
The web console end-to-end test failed in [this build](https://app.travis-ci.com/github/apache/druid/jobs/583131132) with a timeout in the MSQ tests: ```text FAIL e2e-tests/reindexing.spec.ts (56.929 s) ● Reindexing from Druid › Reindex datasource from dynamic to range partitions page.waitForSelector: Timeout 30000ms exceeded. =========================== logs =========================== waiting for selector ".raw-lines" to be visible ============================================================ 73 | private async validateConnect(validator: (preview: string) => void) { 74 | const previewSelector = '.raw-lines'; > 75 | await this.page.waitForSelector(previewSelector); | ^ 76 | const preview = await this.page.$eval(previewSelector, el => (el as HTMLTextAreaElement).value); 77 | validator(preview); 78 | } at DataLoader.<anonymous> (e2e-tests/component/load-data/data-loader.ts:75:21) at node_modules/tslib/tslib.js:117:75 at __awaiter (node_modules/tslib/tslib.js:113:16) at DataLoader.validateConnect (e2e-tests/component/load-data/data-loader.ts:51:38) at DataLoader.<anonymous> (e2e-tests/component/load-data/data-loader.ts:68:16) at fulfilled (node_modules/tslib/tslib.js:114:62) ``` And: ```text FAIL e2e-tests/multi-stage-query.spec.ts (302.319 s) ● Multi-stage query › runs a query that reads external data thrown: "Exceeded timeout of 300000 ms for a test. Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test." 44 | }); 45 | > 46 | it('runs a query that reads external data', async () => { | ^ 47 | await saveScreenshotIfError('multi-stage-query', page, async () => { 48 | const workbench = new WorkbenchOverview(page, UNIFIED_CONSOLE_URL); 49 | const results = await workbench.runQuery(`WITH ext AS (SELECT * at e2e-tests/multi-stage-query.spec.ts:46:3 at Object.<anonymous> (e2e-tests/multi-stage-query.spec.ts:29:1) ``` It is possible that the failure is related to a bug in the branch, or the timeout may be due to some other issue. If the timeout is due to a failed query, then the tests should handle query failures. The commit in question did have a bug in a scan query. If that caused a query to fail, it would have failed immediately, not hang forever. Perhaps these tests do not detect query failure and instead wait for a success that never comes? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
