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

Update elastic-agent-system-metrics #38219

Conversation

fearful-symmetry
Copy link
Contributor

Proposed commit message

Update elastic-agent-system-metrics to bring in the fix for elastic/elastic-agent-system-metrics#129

@fearful-symmetry fearful-symmetry requested a review from a team as a code owner March 7, 2024 16:03
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 7, 2024
Copy link
Contributor

mergify bot commented Mar 7, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @fearful-symmetry? 🙏.
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

@fearful-symmetry fearful-symmetry added backport-v7.12.0 Automated backport with mergify bugfix backport-v8.13.0 Automated backport with mergify and removed backport-v7.12.0 Automated backport with mergify labels Mar 7, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 7, 2024

💚 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: 2024-03-07T16:06:06.281+0000

  • Duration: 169 min 14 sec

Test stats 🧪

Test Results
Failed 0
Passed 29149
Skipped 2046
Total 31195

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

@pierrehilbert pierrehilbert added the Team:Elastic-Agent Label for the Agent team label Mar 7, 2024
@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 Mar 7, 2024
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 7, 2024

@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 7, 2024

@fearful-symmetry
Copy link
Contributor Author

I...think the CI errors are unrelated?

@pierrehilbert
Copy link
Collaborator

Doesn't seem to be related! @pazone are those failures something you are aware of?

@pierrehilbert
Copy link
Collaborator

@fearful-symmetry should we continue with #38229 ?

@fearful-symmetry
Copy link
Contributor Author

@pierrehilbert Oops, forgot about dependabot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v8.13.0 Automated backport with mergify bugfix Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants