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.0](backport #30746) Ignore bugfix version when running version compatibility check against Elasticsearch #30749

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 9, 2022

This is an automatic backport of pull request #30746 done by Mergify.
Cherry-pick of 46be42e has failed:

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

You are currently cherry-picking commit 46be42e7d5.
  (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:   libbeat/common/version.go
	modified:   libbeat/common/version_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/cmd/instance/beat.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

…t Elasticsearch (#30746)

(cherry picked from commit 46be42e)

# Conflicts:
#	libbeat/cmd/instance/beat.go
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 9, 2022
@mergify mergify bot assigned kvch Mar 9, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 9, 2022
@botelastic
Copy link

botelastic bot commented Mar 9, 2022

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

@kvch kvch closed this Mar 9, 2022
@mergify mergify bot deleted the mergify/bp/8.0/pr-30746 branch March 9, 2022 15:47
@elasticmachine
Copy link
Collaborator

💔 Build 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-09T15:25:53.625Z&rangeTo=2022-03-09T15:45:53.625Z&transactionName=BUILD Beats/beats/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=004f0e89d8eed9fc6560ceec9448e545&transactionId=bb6e0a71c1afd536)

Expand to view the summary

Build stats

  • Start Time: 2022-03-09T15:35:53.625+0000

  • Duration: 20 min 35 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

Steps errors 17

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/auditbeat-lint - make -C x-pack/auditbeat check;make -C x-pack/auditbeat update;make -C aud
  • Took 1 min 23 sec . View more details here
  • Description: make -C x-pack/auditbeat check;make -C x-pack/auditbeat update;make -C auditbeat check;make -C auditbeat update;make check-no-changes;
x-pack/filebeat-lint - make -C x-pack/filebeat check;make -C x-pack/filebeat update;make -C filebe
  • Took 2 min 35 sec . View more details here
  • Description: make -C x-pack/filebeat check;make -C x-pack/filebeat update;make -C filebeat check;make -C filebeat update;make check-no-changes;
x-pack/functionbeat-lint - make -C x-pack/functionbeat check;make -C x-pack/functionbeat update;ma
  • Took 1 min 16 sec . View more details here
  • Description: make -C x-pack/functionbeat check;make -C x-pack/functionbeat update;make check-no-changes;
x-pack/heartbeat-lint - make -C x-pack/heartbeat check;make -C x-pack/heartbeat update;make -C hea
  • Took 1 min 18 sec . View more details here
  • Description: make -C x-pack/heartbeat check;make -C x-pack/heartbeat update;make -C heartbeat check;make -C heartbeat update;make check-no-changes;
x-pack/libbeat-lint - make -C x-pack/libbeat check;make -C x-pack/libbeat update;make check-no-cha
  • Took 1 min 18 sec . View more details here
  • Description: make -C x-pack/libbeat check;make -C x-pack/libbeat update;make check-no-changes;
x-pack/metricbeat-lint - make -C x-pack/metricbeat check;make -C x-pack/metricbeat update;make -C
  • Took 2 min 0 sec . View more details here
  • Description: make -C x-pack/metricbeat check;make -C x-pack/metricbeat update;make -C metricbeat check;make -C metricbeat update;make check-no-changes;
x-pack/osquerybeat-lint - make -C x-pack/osquerybeat check;make -C x-pack/osquerybeat update;make
  • Took 1 min 50 sec . View more details here
  • Description: make -C x-pack/osquerybeat check;make -C x-pack/osquerybeat update;make check-no-changes;
x-pack/packetbeat-lint - make -C packetbeat check;make -C packetbeat update;make check-no-changes;
  • Took 1 min 15 sec . View more details here
  • Description: make -C packetbeat check;make -C packetbeat update;make check-no-changes;
x-pack/winlogbeat-lint-immutable && ubuntu-18 - make -C x-pack/winlogbeat check;make -C x-pack/winl
  • Took 1 min 22 sec . View more details here
  • Description: make -C x-pack/winlogbeat check;make -C x-pack/winlogbeat update;make -C winlogbeat check;make -C winlogbeat update;make check-no-changes;
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 2'

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request 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