Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download successful downloads when a known job-type is complete

[kibanamachine]

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
    at /dev/shm/workspace/parallel/6/kibana/x-pack/plugins/reporting/server/routes/jobs.test.ts:254:5
    at _dispatchDescribe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:30:5)
    at /dev/shm/workspace/parallel/6/kibana/x-pack/plugins/reporting/server/routes/jobs.test.ts:237:3
    at _dispatchDescribe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:30:5)
    at Object.<anonymous> (/dev/shm/workspace/parallel/6/kibana/x-pack/plugins/reporting/server/routes/jobs.test.ts:20:1)
    at Runtime._execModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:746:10)
    at jestAdapter (/dev/shm/workspace/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at runTestInternal (/dev/shm/workspace/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/dev/shm/workspace/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/dev/shm/workspace/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

First failure: Jenkins Build

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[tsullivan]

Several x-pack/plugins/reporting/server/routes jest tests failed once on Jan 25, with a couple more on Jan 27 and 28.

• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download when a job is incomplete #89195
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download when a job fails #89196
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download successful downloads succeeds when security is not there or disabled #89198
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download successful downloads when a known job-type is complete #89197
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download successful downloads doesn't encode output-content for non-specified job-types #89199
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes/diagnostic - POST /diagnose/browser cleans up process and subscribers #89369
• Failing test: X-Pack Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download returns 404 if job not found #89518
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download fails on unauthenticated users #89656
• Failing test: Jest Tests.x-pack/plugins/reporting/server/routes - GET /api/reporting/jobs/download fails on users without the appropriate role #89657

These look more like an temporary issue rather than a valid failure, since the failures were each only logged once, and haven't failed again in the last 35 days. Also, the fact that they are all Jest tests is suspicious