Skip to content

[7.15](backport #27178) libbeat/cmd/instance: ensure test config file has appropriate permissions#27797

Merged
efd6 merged 2 commits into7.15from
mergify/bp/7.15/pr-27178
Sep 13, 2021
Merged

[7.15](backport #27178) libbeat/cmd/instance: ensure test config file has appropriate permissions#27797
efd6 merged 2 commits into7.15from
mergify/bp/7.15/pr-27178

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Sep 8, 2021

This is an automatic backport of pull request #27178 done by Mergify.
Cherry-pick of 627b7a8 has failed:

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

You are currently cherry-picking commit 627b7a8b3a.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/cmd/instance/beat_test.go

no changes added to commit (use "git add" and/or "git commit -a")

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.io/

…ions (#27178)

Git does not store r/w permissions, instead depending on the host system's
umask. On some systems the default umask is 0o002, meaning that the test
config file is checked out with g+w permission, causing the test to fail.

This change ensures that the test config is owner-exclusive write before
running the test. It also adds checks to currently ineffective error
assignments.

(cherry picked from commit 627b7a8)

# Conflicts:
#	libbeat/cmd/instance/beat_test.go
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Sep 8, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 8, 2021
@botelastic
Copy link
Copy Markdown

botelastic bot commented Sep 8, 2021

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

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Sep 8, 2021

💚 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: 2021-09-09T10:08:03.198+0000

  • Duration: 149 min 12 sec

  • Commit: a9d1da8

Test stats 🧪

Test Results
Failed 0
Passed 53004
Skipped 5268
Total 58272

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 53004
Skipped 5268
Total 58272

@marc-gr
Copy link
Copy Markdown
Contributor

marc-gr commented Sep 9, 2021

/test

1 similar comment
@P1llus
Copy link
Copy Markdown
Member

P1llus commented Sep 9, 2021

/test

<<<<<<< HEAD
=======
assert.NoError(t, err)
api_key, err := kibanaConfig.String("api_key", -1)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to remove the actual tests as well?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this test was added recently and does not exist in 7.15. This was the cause of the merge conflict as can be seen in the files changed overview.

@efd6 efd6 merged commit 5253eea into 7.15 Sep 13, 2021
@mergify mergify bot deleted the mergify/bp/7.15/pr-27178 branch September 13, 2021 01:48
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.

5 participants