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: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/overview/cti_link_panel·cy·ts - CTI Link Panel renders disabled threat intel module as expected renders disabled threat intel module as expected #165765

Open
kibanamachine opened this issue Sep 5, 2023 · 4 comments
Open

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/overview/cti_link_panel·cy·ts - CTI Link Panel renders disabled threat intel module as expected renders disabled threat intel module as expected #165765

kibanamachine opened this issue Sep 5, 2023 · 4 comments
Assignees
@nkhristinin
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Threat Intel legit-flake Test was triaged and marked as an actual flake. Team:Detection Engine Security Solution Detection Engine Area 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

A test failed on a tracked branch

CypressError: `cy.visit()` failed trying to load:

https://localhost:5626/app/security/overview?timerange=(global%3A(linkTo%3A!(timeline)%2Ctimerange%3A(from%3A1547914976217%2CfromStr%3A%272019-01-19T16%3A22%3A56.217Z%27%2Ckind%3Arelative%2Cto%3A1579537385745%2CtoStr%3Anow))%2Ctimeline%3A(linkTo%3A!(global)%2Ctimerange%3A(from%3A1547914976217%2CfromStr%3A%272019-01-19T16%3A22%3A56.217Z%27%2Ckind%3Arelative%2Cto%3A1579537385745%2CtoStr%3Anow)))

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`.

If you do not want status codes to cause failures pass the option: `failOnStatusCode: false`
    at <unknown> (https://localhost:5626/__cypress/runner/cypress_runner.js:147661:84)
    at visitFailedByErr (https://localhost:5626/__cypress/runner/cypress_runner.js:147069:12)
    at <unknown> (https://localhost:5626/__cypress/runner/cypress_runner.js:147644:13)
    at tryCatcher (https://localhost:5626/__cypress/runner/cypress_runner.js:18744:23)
    at Promise._settlePromiseFromHandler (https://localhost:5626/__cypress/runner/cypress_runner.js:16679:31)
    at Promise._settlePromise (https://localhost:5626/__cypress/runner/cypress_runner.js:16736:18)
    at Promise._settlePromise0 (https://localhost:5626/__cypress/runner/cypress_runner.js:16781:10)
    at Promise._settlePromises (https://localhost:5626/__cypress/runner/cypress_runner.js:16857:18)
    at _drainQueueStep (https://localhost:5626/__cypress/runner/cypress_runner.js:13451:12)
    at _drainQueue (https://localhost:5626/__cypress/runner/cypress_runner.js:13444:9)
    at ../../node_modules/bluebird/js/release/async.js.Async._drainQueues (https://localhost:5626/__cypress/runner/cypress_runner.js:13460:5)
    at Async.drainQueues (https://localhost:5626/__cypress/runner/cypress_runner.js:13330:14)
From Your Spec Code:
    at visit (webpack:///./tasks/login.ts:360:5)
    at Context.eval (webpack:///./e2e/overview/cti_link_panel.cy.ts:24:10)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 5, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 5, 2023
@kibanamachine kibanamachine added the Team:Detection Engine Security Solution Detection Engine Area label Sep 5, 2023
@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 5, 2023
@jpdjere jpdjere mentioned this issue Oct 18, 2023
Closed
@jpdjere
Copy link
Contributor

jpdjere commented Oct 19, 2023 •
edited
Loading

Investigated in #169246

While the error reported in this issue is not the same as why the test is failing on the flaky test runner, the tests for cti_link_panel.cy.ts are consistingly failing, so marking this issue as legit-flake for the @elastic/security-detection-engine to investigate.

cc @yctercero

@jpdjere jpdjere added the legit-flake Test was triaged and marked as an actual flake. label Oct 19, 2023
@jpdjere jpdjere mentioned this issue Nov 6, 2023
Closed
@yctercero yctercero mentioned this issue Nov 15, 2023
Closed
@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Dec 15, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@yctercero
Copy link
Contributor

Hey @nkhristinin ! When you're back, would you mind taking a look at this one?

@yctercero yctercero removed their assignment Feb 7, 2024
@yctercero yctercero added Test:Cypress Team:Detection Engine Security Solution Detection Engine Area and removed Team:Detection Engine Security Solution Detection Engine Area Test:Cypress labels Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nkhristinin nkhristinin

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Threat Intel legit-flake Test was triaged and marked as an actual flake. Team:Detection Engine Security Solution Detection Engine Area 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
6 participants
@jpdjere @banderror @nkhristinin @yctercero @elasticmachine @kibanamachine