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

[7.17](backport #2213) chore: define provider for each test suite#2219

Merged
mdelapenya merged 2 commits into7.17from
mergify/bp/7.17/pr-2213
Mar 9, 2022
Merged

[7.17](backport #2213) chore: define provider for each test suite#2219
mdelapenya merged 2 commits into7.17from
mergify/bp/7.17/pr-2213

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Mar 9, 2022

This is an automatic backport of pull request #2213 done by Mergify.
Cherry-pick of 2ddece6 has failed:

On branch mergify/bp/7.17/pr-2213
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 2ddece66.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .ci/.e2e-platforms.yaml
	modified:   .ci/Jenkinsfile
	modified:   .ci/README.md
	modified:   .ci/ansible/tasks/setup_test_script.yml
	modified:   e2e/_suites/fleet/stand-alone.go
	modified:   internal/kibana/fleet.go
	modified:   internal/kibana/policies.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .ci/.e2e-tests-for-elastic-agent.yaml
	both modified:   .ci/.e2e-tests.yaml
	both modified:   README.md
	both modified:   e2e/_suites/fleet/fleet.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

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

@mdelapenya
chore: define provider for each test suite (#2213)
98f74db 
* chore: preset the provider at suite or/and scenario level

* docs: document the CI descriptor for the platform support

* docs: describe each platform

* fix: typo

* chore: declare platforms just once

* docs: document machine dependencies

* docs: link to CI infra documentation

* fix: use right location for the platforms file

* fix: set remote variables only for remote provider

* fix: disable fleet-server for regular standalone deployments

* chore: add ES and kibana endpoints to the logs

* chore: apply docker provider for elastic-agent triggers

* chore: re-enable stand-alone scenarios

* chore: move fleet-server default policy to a constant

* Revert "chore: re-enable stand-alone scenarios"

This reverts commit cbb281f.

(cherry picked from commit 2ddece6)

# Conflicts:
#	.ci/.e2e-tests-for-elastic-agent.yaml
#	.ci/.e2e-tests.yaml
#	README.md
#	e2e/_suites/fleet/fleet.go
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Mar 9, 2022
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Mar 9, 2022 •
edited
Loading

💔 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](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-09T20:49:46.045Z&rangeTo=2022-03-09T21:09:46.045Z&transactionName=BUILD e2e-tests/e2e-testing-mbp/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=49ae78b2b1606eaefa300ad56de59f58&transactionId=7db001ec433a23d3)

Expand to view the summary

Build stats

  • Start Time: 2022-03-09T20:59:46.045+0000

  • Duration: 49 min 53 sec

Test stats 🧪

Test Results
Failed 1
Passed 271
Skipped 0
Total 272

Test errors 1

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

Steps errors 2

Expand to view the steps failures

Shell Script
  • Took 17 min 26 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-2219-2-0a0a8fd4-b9a1-43cd-874c-49b852a43a40/e2essh admin@18.222.251.79 -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '
Archive the artifacts
  • Took 0 min 1 sec . View more details here
  • Description: [2022-03-09T21:48:32.224Z] 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 1

💔 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

🤖 GitHub comments

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

  • /test : Re-trigger the build.

@mdelapenya mdelapenya removed the conflicts There is a conflict in the backported pull request label Mar 9, 2022
@mdelapenya mdelapenya merged commit d4250df into 7.17 Mar 9, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-2213 branch March 9, 2022 22:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

@mdelapenya mdelapenya

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@elasticmachine @mdelapenya