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 API Integration Tests.x-pack/test/api_integration/apis/monitoring/common/mappings_exist·js - apis Monitoring common mappings for es metrics ccr_stats.time_since_last_fetch_millis should exist in the mappings #24588

Closed
kibanamachine opened this issue Oct 25, 2018 · 8 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Monitoring Stack Monitoring team

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 25, 2018

A test failed on a tracked branch


        Error: expected null to not equal null
    at Assertion.assert (node_modules/expect.js/index.js:96:13)
    at Assertion.be.Assertion.equal (node_modules/expect.js/index.js:216:10)
    at Context.it (test/api_integration/apis/monitoring/common/mappings_exist.js:66:43)
    at Object.apply (/var/lib/jenkins/workspace/elastic+kibana+master+multijob-x-pack/kibana/src/functional_test_runner/lib/mocha/wrap_function.js:85:30)
      

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 25, 2018
@joshdover
Copy link
Contributor

@elastic/kibana-monitoring

@joshdover joshdover added the Team:Monitoring Stack Monitoring team label Oct 25, 2018
@joshdover
Copy link
Contributor

@chrisronline This looks like something that was fixed by your changes?

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@chrisronline
Copy link
Contributor

@joshdover Correct! This should be resolved now

@spalger
Copy link
Contributor

spalger commented Oct 26, 2018

Which PR? Trying to find it to backport to 6.x and 6.5...

@chrisronline
Copy link
Contributor

#24593

It's been backported already. We need the snapshot to update for ES 6.x which I think is failing for unrelated reasons

@spalger
Copy link
Contributor

spalger commented Oct 26, 2018

@chrisronline Ah, it's the skip that didn't get back to 6.x and 6.5. I've included a skip in my tests in #24613 (6.x) and #24614 (6.5)

@chrisronline
Copy link
Contributor

We need a fix for this in master actually (until the snapshots are updated)

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:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

4 participants