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

[8.3](backport #32259) Upgrade github.com/elastic/go-sysinfo v1.8.0 => v1.8.1 #32304

Merged
merged 1 commit into from
Jul 11, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 11, 2022

This is an automatic backport of pull request #32259 done by Mergify.
Cherry-pick of 86bb5f3 has failed:

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

You are currently cherry-picking commit 86bb5f3799.
  (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:
	modified:   CHANGELOG.next.asciidoc
	modified:   go.mod
	modified:   go.sum

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt

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

@mergify mergify bot requested a review from a team as a code owner July 11, 2022 13:39
@mergify mergify bot requested review from cmacknz and leehinman and removed request for a team July 11, 2022 13:39
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jul 11, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 11, 2022
@botelastic
Copy link

botelastic bot commented Jul 11, 2022

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

@elasticmachine
Copy link
Collaborator

elasticmachine commented Jul 11, 2022

💚 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: 2022-07-11T14:25:49.878+0000

  • Duration: 110 min 31 sec

Test stats 🧪

Test Results
Failed 0
Passed 22330
Skipped 1932
Total 24262

💚 Flaky test report

Tests succeeded.

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

@andrewkroh andrewkroh removed the conflicts There is a conflict in the backported pull request label Jul 11, 2022
@andrewkroh andrewkroh merged commit 50960f2 into 8.3 Jul 11, 2022
@mergify mergify bot deleted the mergify/bp/8.3/pr-32259 branch July 11, 2022 17:31
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants