This repository was archived by the owner on Sep 17, 2024. It is now read-only.

[8.1](backport #2130) chore: use trace level in logs#2190

Merged

mdelapenya merged 2 commits into8.1from

mergify/bp/8.1/pr-2130

Mar 8, 2022

Contributor

mergify bot commented Mar 1, 2022

This is an automatic backport of pull request #2130 done by Mergify.

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

@Mergifyio refresh will re-evaluate the rules
@Mergifyio rebase will rebase this PR on its base branch
@Mergifyio update will merge the base branch into this PR
@Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

look at your merge queues
generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com


          chore: use trace level in logs (#2130)

e4ea351

(cherry picked from commit d393d27)

mergify bot assigned mdelapenya

Contributor

elasticmachine commented Mar 1, 2022 •

edited

Loading

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
[](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-07T06:30:04.480Z&rangeTo=2022-03-07T06:50:04.480Z&transactionName=BUILD e2e-tests/e2e-testing-mbp/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=731060a0aaa23176d8fa178c5093db9e&transactionId=39ca9dc4c3beec67)

Expand to view the summary

Build stats

Start Time: 2022-03-07T06:40:04.480+0000
Duration: 69 min 35 sec

Test stats 🧪

Test	Results
Failed	5
Passed	267
Skipped	0
Total	272

Test errors

Expand to view the tests failures

`Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone`

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded

no stacktrace

`Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone`

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:container-in-pod"

no stacktrace

`Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone`

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:cronjob-container": context deadline exceeded

no stacktrace

`Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone`

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-failing-pod": context deadline exceeded

no stacktrace

`Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone`

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:redis": context deadline exceeded

no stacktrace

Steps errors

Expand to view the steps failures

`Shell Script`

Took 44 min 11 sec . View more details here
Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2190-3-026b775f-dcce-4e57-a769-b4e4c223e5be/e2essh admin@3.19.246.54 -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '

`Archive the artifacts`

Took 0 min 0 sec . View more details here
Description: [2022-03-07T07:48:33.856Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone
Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone
Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone
Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone
Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

mdelapenya mentioned this pull request

[automation] update elastic stack version for testing 8.1.0-fbfb1f9e #2199

Closed

Contributor Author

mergify bot commented Mar 7, 2022

This pull request has not been merged yet. Could you please review and merge it @mdelapenya? 🙏


          Merge branch '8.1' into mergify/bp/8.1/pr-2130

c768ba1

mdelapenya merged commit 4a65e8d into 8.1

mergify bot deleted the mergify/bp/8.1/pr-2130 branch

March 8, 2022 07:40

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet