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

Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/bwc_shared_urls·js - dashboard app using legacy data bwc shared urls "before all" hook in "bwc shared urls" #51038

Closed
kibanamachine opened this issue Nov 19, 2019 · 5 comments · Fixed by #52601
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 19, 2019

A test failed on a tracked branch

{ [resource_not_found_exception] task [RmAhOyQCT1atMigOKDUE_w:1437] isn't running and hasn't stored its results :: {"path":"/_tasks/RmAhOyQCT1atMigOKDUE_w%3A1437","query":{},"statusCode":404,"response":"{\"error\":{\"root_cause\":[{\"type\":\"resource_not_found_exception\",\"reason\":\"task [RmAhOyQCT1atMigOKDUE_w:1437] isn't running and hasn't stored its results\"}],\"type\":\"resource_not_found_exception\",\"reason\":\"task [RmAhOyQCT1atMigOKDUE_w:1437] isn't running and hasn't stored its results\"},\"status\":404}"}
    at respond (node_modules/elasticsearch/src/lib/transport.js:349:15)
    at checkRespForFailure (node_modules/elasticsearch/src/lib/transport.js:306:7)
    at HttpConnector.<anonymous> (node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
    at IncomingMessage.wrapper (node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)
    at endReadableNT (_stream_readable.js:1103:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  status: 404,
  displayName: 'NotFound',
  message:
   '[resource_not_found_exception] task [RmAhOyQCT1atMigOKDUE_w:1437] isn\'t running and hasn\'t stored its results',
  path: '/_tasks/RmAhOyQCT1atMigOKDUE_w%3A1437',
  query: {},
  body:
   { error:
      { root_cause: [Array],
        type: 'resource_not_found_exception',
        reason:
         'task [RmAhOyQCT1atMigOKDUE_w:1437] isn\'t running and hasn\'t stored its results' },
     status: 404 },
  statusCode: 404,
  response:
   '{"error":{"root_cause":[{"type":"resource_not_found_exception","reason":"task [RmAhOyQCT1atMigOKDUE_w:1437] isn\'t running and hasn\'t stored its results"}],"type":"resource_not_found_exception","reason":"task [RmAhOyQCT1atMigOKDUE_w:1437] isn\'t running and hasn\'t stored its results"},"status":404}',
  toString: [Function],
  toJSON: [Function] }

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 19, 2019
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger spalger closed this as completed Nov 19, 2019
@spalger spalger reopened this Dec 4, 2019
@spalger
Copy link
Contributor

spalger commented Dec 4, 2019

There has been an uptick in flaky failures in PRs for this, mostly seeing 409 conflicts when trying to clear the buildNum uiSetting, which is strange. I'll look more into this in a bit

image

@kibanamachine

This comment has been minimized.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants