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.

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

add filebeat integration test for shipper input/output #36349

Merged
merged 5 commits into from
Sep 7, 2023

Conversation

leehinman
Copy link
Contributor

Proposed commit message

Add filebeat shipper input/output integration test

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
    - [ ] I have made corresponding changes to the documentation
    - [ ] I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
    - [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

Run go integration tests

cd x-pack/filebeat
mage goUnitTest

Just run this test

cd x-pack/filebeat
mage docker:composeUp
go test ./tests/integration -count 1 -tags integration -run TestShipperInputOutput

Related issues

@leehinman leehinman added enhancement Team:Elastic-Agent Label for the Agent team labels Aug 16, 2023
@leehinman leehinman requested a review from a team as a code owner August 16, 2023 18:16
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 16, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Aug 16, 2023
@mergify
Copy link
Contributor

mergify bot commented Aug 16, 2023

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @leehinman? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

elasticmachine commented Aug 16, 2023

❕ Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

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

Expand to view the summary

Build stats

  • Start Time: 2023-09-05T14:18:58.749+0000

  • Duration: 56 min 23 sec

Test stats 🧪

Test Results
Failed 0
Passed 27431
Skipped 1937
Total 29368

Steps errors 1

Expand to view the steps failures

Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

🤖 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!)

@leehinman leehinman force-pushed the filebeat_shipper_integration_test branch from fd21245 to 4c599cc Compare September 5, 2023 15:08
@elasticmachine
Copy link
Collaborator

elasticmachine commented Sep 5, 2023

💚 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-09-06T21:05:33.464+0000

  • Duration: 90 min 3 sec

Test stats 🧪

Test Results
Failed 0
Passed 28225
Skipped 2015
Total 30240

💚 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!)

@leehinman leehinman merged commit 6cf8778 into elastic:main Sep 7, 2023
9 checks passed
@leehinman leehinman deleted the filebeat_shipper_integration_test branch September 7, 2023 00:26
@xudengping
Copy link

what's shipper input

@cmacknz
Copy link
Member

cmacknz commented Oct 13, 2023

See #35135 for context on what this was. The plan has changed here however and we won't be using this input.

Scholar-Li pushed a commit to Scholar-Li/beats that referenced this pull request Feb 5, 2024
* add filebeat integration test for shipper input/output
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants