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: X-Pack Jest Tests.x-pack/legacy/plugins/uptime/public/components/functional/location_map/__tests__ - LocationStatusTags component renders properly against props #54818

Closed
kibanamachine opened this issue Jan 14, 2020 · 4 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: expect(received).toMatchSnapshot()

Snapshot name: `LocationStatusTags component renders properly against props 1`

- Snapshot
+ Received

@@ -33,11 +33,11 @@
          >
            <EuiText
              size="m"
            >
              <styled.div>
-               Berlin
+               Islamabad
              </styled.div>
            </EuiText>
          </EuiBadge>
          <styled.span>
            <EuiText
@@ -55,11 +55,11 @@
          >
            <EuiText
              size="m"
            >
              <styled.div>
-               Islamabad
+               Berlin
              </styled.div>
            </EuiText>
          </EuiBadge>
          <styled.span>
            <EuiText
    at Object.it (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/x-pack/legacy/plugins/uptime/public/components/functional/location_map/__tests__/location_status_tags.test.tsx:41:23)
    at Object.asyncJestTest (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:102:37)
    at resolve (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/queueRunner.js:43:12)
    at new Promise (<anonymous>)
    at mapper (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/queueRunner.js:26:19)
    at promise.then (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/queueRunner.js:73:41)
    at process._tickCallback (internal/process/next_tick.js:68:7)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 14, 2020
@elasticmachine
Copy link
Contributor

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

@brianseeders brianseeders added skipped-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability labels Jan 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@brianseeders
Copy link
Contributor

Just skipped on master, looks like maybe the order of some elements can change between runs?

@shahzad31
Copy link
Contributor

It's fixed in #54867

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 skipped-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability
Projects
None yet
Development

No branches or pull requests

4 participants