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

[automation] update elastic stack version for testing 8.1.0-574d4d37#2194

Closed
ghost wants to merge 1 commit into8.1from
update-stack-version-8.1.0-574d4d37-20220302051326
Closed

[automation] update elastic stack version for testing 8.1.0-574d4d37#2194
ghost wants to merge 1 commit into8.1from
update-stack-version-8.1.0-574d4d37-20220302051326

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Mar 2, 2022

What

Bump stack version with the latest one.

Further details

[start_time:Tue, 1 Mar 2022 12:13:39 GMT, release_branch:8.1, prefix:, end_time:Tue, 1 Mar 2022 17:11:51 GMT, manifest_version:2.0.0, version:8.1.0-SNAPSHOT, branch:8.1, build_id:8.1.0-574d4d37, build_duration_seconds:17892]

@ghost ghost added automation backport-skip Skip notification from the automated backport with mergify dependency labels Mar 2, 2022
@ghost ghost requested review from a team and v1v and removed request for a team March 2, 2022 05:13
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Mar 2, 2022

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-03-02T05:13:45.813+0000

  • Duration: 76 min 5 sec

Test stats 🧪

Test Results
Failed 5
Passed 267
Skipped 0
Total 272

Test errors 5

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 2

Expand to view the steps failures

Shell Script
  • Took 44 min 13 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-2194-1-d3cac030-cd39-4c70-b82c-4b7a6b8e143e/e2essh admin@18.117.114.28 -- '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-02T06:29:36.761Z] 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 5

💔 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
Copy link
Copy Markdown
Contributor

mdelapenya commented Mar 2, 2022

@ChrsMark I started to see these 5 errors as consistent in 8.1. Is there anything in your mind for the root cause?

@mdelapenya mdelapenya mentioned this pull request Mar 2, 2022
Merged
@mdelapenya mdelapenya closed this Mar 3, 2022
@mergify mergify bot deleted the update-stack-version-8.1.0-574d4d37-20220302051326 branch March 3, 2022 09:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@v1v v1v Awaiting requested review from v1v

Assignees

No one assigned

Labels

automation backport-skip Skip notification from the automated backport with mergify dependency

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@elasticmachine @mdelapenya