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.

Sign up for GitHub

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

Jump to bottom

[8.7](backport #34870) Add test for the processor re-use issue #34881

Merged
merged 1 commit into from
Mar 21, 2023
Merged

[8.7](backport #34870) Add test for the processor re-use issue #34881

merged 1 commit into from
Mar 21, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 21, 2023 •
edited by zube bot
Loading

This is an automatic backport of pull request #34870 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

@rdner @mergify
Add test for the processor re-use issue (#34870)
c893981 
It's a follow-up to #34761

This test makes sure that none of the critical configuration fields
are re-used between instances of the pipeline client.

(cherry picked from commit 3d917c8)
@mergify mergify bot requested a review from a team as a code owner March 21, 2023 17:12
@mergify mergify bot requested review from belimawr and leehinman and removed request for a team March 21, 2023 17:12
@mergify mergify bot added the backport label Mar 21, 2023
@mergify mergify bot assigned rdner Mar 21, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 21, 2023
@botelastic
Copy link

botelastic bot commented Mar 21, 2023

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

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: 2023-03-21T17:13:00.475+0000

  • Duration: 70 min 41 sec

Test stats 🧪

Test Results
Failed 0
Passed 7569
Skipped 746
Total 8315

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@rdner rdner merged commit d920e81 into 8.7 Mar 21, 2023
@rdner rdner deleted the mergify/bp/8.7/pr-34870 branch March 21, 2023 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@belimawr belimawr Awaiting requested review from belimawr belimawr is a code owner automatically assigned from elastic/elastic-agent-data-plane

@leehinman leehinman Awaiting requested review from leehinman leehinman is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@rdner rdner

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @rdner