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: Security Solution Cypress.x-pack/plugins/security_solution/public/management/cypress/e2e/response_actions/response_console/scan·cy·ts - Response console Scan operation: "before all" hook for ""scan --path" - should scan a file" "before all" hook for ""scan --path" - should scan a file" #187932

Closed
kibanamachine opened this issue Jul 10, 2024 · 144 comments · Fixed by #188013, #199416 or #210845
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 10, 2024

A test failed on a tracked branch

-----
Security Solution Cypress.x-pack/plugins/security_solution/public/management/cypress/e2e/response_actions/response_console/scan·cy·ts
Response console Scan operation: "before all" hook for ""scan --path" - should scan a file" "before all" hook for ""scan --path" - should scan a file"

Failure:
--------
CypressError: `cy.task('createEndpointHost')` failed with the following error:

> Request failed with status code 503: "<html>\r\n<head><title>503 Service Temporarily Unavailable</title></head>\r\n<body>\r\n<center><h1>503 Service Temporarily Unavailable</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
(Request: get https://artifacts-api.elastic.co/v1/versions)

https://on.cypress.io/api/task

Because this error occurred during a `before all` hook we are skipping the remaining tests in the current suite: `Scan operation:`

Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail
    at <unknown> (http://localhost:5647/__cypress/runner/cypress_runner.js:135281:70)
    at tryCatcher (http://localhost:5647/__cypress/runner/cypress_runner.js:1807:23)
    at Promise._settlePromiseFromHandler (http://localhost:5647/__cypress/runner/cypress_runner.js:1519:31)
    at Promise._settlePromise (http://localhost:5647/__cypress/runner/cypress_runner.js:1576:18)
    at Promise._settlePromise0 (http://localhost:5647/__cypress/runner/cypress_runner.js:1621:10)
    at Promise._settlePromises (http://localhost:5647/__cypress/runner/cypress_runner.js:1697:18)
    at _drainQueueStep (http://localhost:5647/__cypress/runner/cypress_runner.js:2407:12)
    at _drainQueue (http://localhost:5647/__cypress/runner/cypress_runner.js:2400:9)
    at Async._drainQueues (http://localhost:5647/__cypress/runner/cypress_runner.js:2416:5)
    at Async.drainQueues (http://localhost:5647/__cypress/runner/cypress_runner.js:2286:14)
From Your Spec Code:
    at createEndpointHost (webpack:///./tasks/create_endpoint_host.ts:16:12)
    at Context.eval (webpack:///./e2e/response_actions/response_console/scan.cy.ts:62:40)

From Node.js Internals:
  FormattedAxiosError: Request failed with status code 503: "<html>\r\n<head><title>503 Service Temporarily Unavailable</title></head>\r\n<body>\r\n<center><h1>503 Service Temporarily Unavailable</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
  (Request: get https://artifacts-api.elastic.co/v1/versions)
      at catchAxiosErrorFormatAndThrow (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/x-pack/plugins/security_solution/common/endpoint/format_axios_error.ts:70:11)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async RetryOperation._fn (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/node_modules/p-retry/index.js:50:12)
  ----- original error -----
  AxiosError: Request failed with status code 503
      at settle (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/node_modules/axios/lib/core/settle.js:19:12)
      at IncomingMessage.handleStreamEnd (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/node_modules/axios/lib/adapters/http.js:599:11)
      at IncomingMessage.emit (node:events:531:35)
      at IncomingMessage.emit (node:domain:488:12)
      at endReadableNT (node:internal/streams/readable:1696:12)
      at processTicksAndRejections (node:internal/process/task_queues:82:21)
      at Axios.request (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/node_modules/axios/lib/core/Axios.js:45:41)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async RetryOperation._fn (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730909347220568384/elastic/kibana-on-merge/kibana/node_modules/p-retry/index.js:50:12)

First failure: kibana-on-merge - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 10, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 10, 2024
@kibanamachine kibanamachine added the Team:Defend Workflows “EDR Workflows” sub-team of Security Solution label Jul 10, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 10, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@jbudz
Copy link
Member

jbudz commented Jul 10, 2024

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 94a639f

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue Dec 10, 2024
mistic added a commit that referenced this issue Dec 10, 2024
mistic added a commit that referenced this issue Dec 10, 2024
@mistic
Copy link
Member

mistic commented Dec 10, 2024

Skipped.

main: b211bfd
8.x: fa03ccc
8.17: c7d84b7

CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.16

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.16

ashokaditya added a commit to ashokaditya/kibana that referenced this issue Feb 12, 2025
ashokaditya added a commit that referenced this issue Feb 19, 2025
…210845)

## Summary

Re enables skipped test (which was flaky due to Vagrant not available on
CI).
closes #187932

### Flaky runner
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867
x 50 (1 fail)
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904
x 50 (all pass)

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 19, 2025
…lastic#210845)

## Summary

Re enables skipped test (which was flaky due to Vagrant not available on
CI).
closes elastic#187932

### Flaky runner
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867
x 50 (1 fail)
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904
x 50 (all pass)

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 98b565d)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 19, 2025
…lastic#210845)

## Summary

Re enables skipped test (which was flaky due to Vagrant not available on
CI).
closes elastic#187932

### Flaky runner
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867
x 50 (1 fail)
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904
x 50 (all pass)

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 98b565d)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 19, 2025
…lastic#210845)

## Summary

Re enables skipped test (which was flaky due to Vagrant not available on
CI).
closes elastic#187932

### Flaky runner
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867
x 50 (1 fail)
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904
x 50 (all pass)

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 98b565d)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 19, 2025
…lastic#210845)

## Summary

Re enables skipped test (which was flaky due to Vagrant not available on
CI).
closes elastic#187932

### Flaky runner
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867
x 50 (1 fail)
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904
x 50 (all pass)

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 98b565d)
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 Team:Defend Workflows “EDR Workflows” sub-team of Security Solution
Projects
None yet
6 participants