Skip to content

fix(bk): serverless-beats-tests start failing after merging #10734#10906

Merged
v1v merged 3 commits into
elastic:mainfrom
v1v:fix/beats-agent-serverless-tests-2
Oct 30, 2025
Merged

fix(bk): serverless-beats-tests start failing after merging #10734#10906
v1v merged 3 commits into
elastic:mainfrom
v1v:fix/beats-agent-serverless-tests-2

Conversation

@v1v
Copy link
Copy Markdown
Member

@v1v v1v commented Oct 29, 2025

What does this PR do?

Restore the previous environmental context for the serverless-beats-tests
Run serverless-beats-tests if touching some of the core files.

Why is it important?

Regression, and help with early detection

Checklist

  • I have read and understood the pull request guidelines of this project.
  • 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/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

NA

Only in the CI

This PR triggered:

image

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@v1v v1v self-assigned this Oct 29, 2025
@v1v v1v requested a review from a team as a code owner October 29, 2025 17:36
@v1v v1v requested a review from a team as a code owner October 29, 2025 17:36
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Oct 29, 2025

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

ycombinator
ycombinator previously approved these changes Oct 29, 2025
Copy link
Copy Markdown
Contributor

@ycombinator ycombinator left a comment

Choose a reason for hiding this comment

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

LGTM but I'd also like @pchila to review as he's currently working on trying to improve our CI times.

@ycombinator ycombinator requested a review from pchila October 29, 2025 17:40
Copy link
Copy Markdown
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for addressing that @v1v!

Comment thread .buildkite/pipeline.yml Outdated
Comment thread .buildkite/pipeline.yml
@fr4nc1sc0-r4m0n
Copy link
Copy Markdown
Contributor

We should backport this change to all active branches, right?

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @v1v

@v1v v1v added the backport-active-all Automated backport with mergify to all the active branches label Oct 30, 2025
@v1v v1v merged commit 0a1cf18 into elastic:main Oct 30, 2025
23 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

@Mergifyio backport 8.19 9.1 9.2

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Oct 30, 2025

backport 8.19 9.1 9.2

✅ Backports have been created

Details

mergify Bot pushed a commit that referenced this pull request Oct 30, 2025
…10906)

(cherry picked from commit 0a1cf18)

# Conflicts:
#	.buildkite/hooks/pre-command
#	.buildkite/pipeline.yml
mergify Bot pushed a commit that referenced this pull request Oct 30, 2025
…10906)

(cherry picked from commit 0a1cf18)

# Conflicts:
#	.buildkite/pipeline.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches skip-changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants