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.

Sign up for GitHub

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

Jump to bottom

Failing test: "after all" hook for "Exports a custom rule" - Export rules "after all" hook for "Exports a custom rule" #85679

Closed
kibanamachine opened this issue Dec 10, 2020 · 19 comments
Closed

Failing test: "after all" hook for "Exports a custom rule" - Export rules "after all" hook for "Exports a custom rule" #85679

kibanamachine opened this issue Dec 10, 2020 · 19 comments
Assignees
@peluja1012 @spong
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 10, 2020 •
edited
Loading

A test failed on a tracked branch

CypressError: `cy.request()` failed on:

http://elastic:changeme@localhost:6151/api/detection_engine/rules?rule_id=rule_testing

The response we received from your web server was:

  > 500: Internal Server Error

This was considered a failure because the status code was not `2xx` or `3xx`.

If you do not want status codes to cause failures pass the option: `failOnStatusCode: false`

-----------------------------------------------------------

The request we sent was:

Method: DELETE
URL: http://elastic:changeme@localhost:6151/api/detection_engine/rules?rule_id=rule_testing
Headers: {
  "Connection": "keep-alive",
  "kbn-xsrf": "cypress-creds",
  "user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/87.0.4280.88 Safari/537.36",
  "accept": "*/*",
  "cookie": "sid=Fe26.2**6cbebd2f5c754cca762b9e71a6782178a51a200f9bdabe14a688adb01208b36e*irIIAC4afSZfppbLN78rMQ*XLb9KbvhvAjnkO5QMI3svf-38CgeE9ctQgSwUXtJjb1rouogeLXRmvx6mE6gkm1Focg79CWbOBRRZj1pZnAPeju9ibSNvI3-1Tw0vvyvTfQLUBo09VcdhNrCf9f4c_QmFKSK3k-EbmpfqvDqZzvEvOMuAOfc7NjGHrnEPc03serK5bOYtNrea2IVJuVpTdfVL_Kq-IpQg3dF2TTQMa62Gf5s-i407Rs-eZosQuhdA84**f34f03b7e9bf58d1b6a77fcecda19c6a2f53c4253f66718efdf18cc09cf90cbd*XRAww3-5KQjCR1HpOrQ_lDJs-iFZXFku9onmxy2izZw",
  "accept-encoding": "gzip, deflate",
  "authorization": "Basic ZWxhc3RpYzpjaGFuZ2VtZQ==",
  "content-length": 0
}

-----------------------------------------------------------

The response we got was:

Status: 500 - Internal Server Error
Headers: {
  "content-type": "application/json; charset=utf-8",
  "kbn-name": "kibana-ci-immutable-ubuntu-18-tests-xxl-1607634196457586066",
  "kbn-license-sig": "11a88980626736dd699d8f9f75172106e6a26228aefff99ea2b4f132147816db",
  "cache-control": "private, no-cache, no-store, must-revalidate",
  "content-length": "77",
  "date": "Thu, 10 Dec 2020 21:43:33 GMT",
  "connection": "keep-alive",
  "keep-alive": "timeout=120"
}
Body: {
  "message": "Cannot read property 'arguments' of undefined",
  "status_code": 500
}


https://on.cypress.io/request

Because this error occurred during a `after all` hook we are skipping the remaining tests in the current suite: `Export rules`

Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail
    at http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:158924:21
    at tryCatcher (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:10584:23)
    at Promise._settlePromiseFromHandler (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:8519:31)
    at Promise._settlePromise (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:8576:18)
    at Promise._settlePromise0 (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:8621:10)
    at Promise._settlePromises (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:8701:18)
    at _drainQueueStep (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:5291:12)
    at _drainQueue (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:5284:9)
    at Async.../../node_modules/bluebird/js/release/async.js.Async._drainQueues (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:5300:5)
    at Async.drainQueues (http://elastic:changeme@localhost:6151/__cypress/runner/cypress_runner.js:5170:14)
From Your Spec Code:
    at Object.deleteCustomRule (http://localhost:6151/__cypress/tests?p=cypress/integration/alerts_detection_rules_export.spec.ts:21189:8)
    at Context.eval (http://localhost:6151/__cypress/tests?p=cypress/integration/alerts_detection_rules_export.spec.ts:20298:17)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 10, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@MadameSheema MadameSheema added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detections and Resp Security Detection Response Team and removed failed-test A test failure on a tracked branch, potentially flaky-test labels Dec 12, 2020
@MadameSheema
Copy link
Member

Closing this issue as per the screenshots on the report looks like was a problem with the Kibana snapshot.

@MadameSheema MadameSheema added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 12, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine kibanamachine reopened this Dec 12, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@tylersmalley tylersmalley mentioned this issue Dec 16, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peluja1012 peluja1012

@spong spong

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@peluja1012 @spong @MadameSheema @kibanamachine