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: Jest Tests.x-pack/plugins/actions/server/lib - successfully executes #103037

Closed
kibanamachine opened this issue Jun 23, 2021 · 3 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jun 23, 2021

A test failed on a tracked branch

Error: expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `successfully executes 1`

- Snapshot  -  0
+ Received  + 19

@@ -1,9 +1,28 @@
  Array [
    Array [
      Object {
        "event": Object {
+         "action": "execute-start",
+       },
+       "kibana": Object {
+         "saved_objects": Array [
+           Object {
+             "id": "1",
+             "namespace": "some-namespace",
+             "rel": "primary",
+             "type": "action",
+             "type_id": "test",
+           },
+         ],
+       },
+       "message": "action started: test:1: 1",
+     },
+   ],
+   Array [
+     Object {
+       "event": Object {
          "action": "execute",
          "outcome": "success",
        },
        "kibana": Object {
          "saved_objects": Array [
    at Object.<anonymous> (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/x-pack/plugins/actions/server/lib/action_executor.test.ts:112:43)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at _callCircusTest (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/run.js:212:5)
    at _runTest (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/run.js:149:3)
    at _runTestsForDescribeBlock (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/run.js:63:9)
    at run (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/run.js:25:3)
    at runAndTransformResultsToJestFormat (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)
    at jestAdapter (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:109:19)
    at runTestInternal (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jun 23, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Jun 23, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@jportner jportner added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jun 29, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jun 29, 2021
@ymao1
Copy link
Contributor

ymao1 commented Jun 29, 2021

This was from this PR that got merged and then reverted and then resubmitted

@ymao1 ymao1 closed this as completed Jun 29, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
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:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

5 participants