-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[WIP] Ingest code coverage COVERAGE JOB #54770
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wayneseymour
added
the
release_note:skip
Skip the PR/issue when compiling release notes
label
Jan 14, 2020
Closed
💔 Build FailedHistory
To update your PR or re-run it, just comment with: |
just 15.
script on error. Use set -o xtrace for var expansion and command printing, like how CI works.
💔 Build FailedHistory
To update your PR or re-run it, just comment with: |
💔 Build FailedHistory
To update your PR or re-run it, just comment with: |
wayneseymour
force-pushed
the
ingest-code-coverage
branch
from
April 1, 2020 16:57
f25f172
to
87dfc1d
Compare
wayneseymour
force-pushed
the
ingest-code-coverage
branch
from
April 1, 2020 20:42
4179bff
to
f229c24
Compare
💔 Build Failed
Failed CI StepsTest FailuresKibana Pipeline / kibana-xpack-agent / Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/documents_source/docvalue_fields·js.maps app documents source docvalue_fields should only fetch geo_point field and data driven styling fieldsStandard Out
Stack Trace
Kibana Pipeline / kibana-xpack-agent / Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/documents_source/docvalue_fields·js.maps app documents source docvalue_fields should only fetch geo_point field and data driven styling fieldsStandard Out
Stack Trace
Kibana Pipeline / kibana-xpack-agent / X-Pack API Integration Tests.x-pack/test/api_integration/apis/ml/calculate_model_memory_limit·ts.apis Machine Learning calculate model memory limit calculates the model memory limit 4 influencers, split by customer_id and filtering by country codeStandard Out
Stack Trace
History
To update your PR or re-run it, just comment with: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
automation
Feature:CI
Continuous integration
release_note:skip
Skip the PR/issue when compiling release notes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Ingest code coverage, run against the master branch, to an es cluster.
Tested here: https://kibana-ci.elastic.co/job/elastic+kibana+code-coverage/
Same code as #60536
However, this is pipeline job, run in ci via a coverage-specific pipeline