Skip to content

[8.19] (backport #18386) Backport smart exhaustive tests#18389

Merged
v1v merged 2 commits into
8.19from
mergify/bp/8.19/pr-18386
Nov 3, 2025
Merged

[8.19] (backport #18386) Backport smart exhaustive tests#18389
v1v merged 2 commits into
8.19from
mergify/bp/8.19/pr-18386

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Nov 1, 2025

Backports the following commits:

bf89f43 (HEAD, upstream/main) chore: remove test file for exhaustive tests and normalise github commands (#18384)
02aa5e1 bk(smart exhaustive tests): tune the steps to support GH comments and changesets (#18383)
be64ebf bk: fix regex and add new file (#18382)
fc9ad7f feat(ci): support exhaustive tests for PRs (code changes or GH comment) (#18327)

To solve:

https://buildkite.com/elastic/logstash-smart-exhaustive-tests-pipeline/builds/32#019a3b6c-873e-4817-8fe1-4552c0fba68a

2025-10-31 10:59:54 PDT
Running agent environment hook
2025-10-31 10:59:56 PDT
Preparing working directory
2025-10-31 11:00:00 PDT
Running commands
2025-10-31 11:00:00 PDT
$ buildkite-agent pipeline upload .buildkite/smart_exhaustive_tests_pipeline.yml
2025-10-31 11:00:00 PDT
2025-10-31 18:00:00 INFO   Reading pipeline configs from [".buildkite/smart_exhaustive_tests_pipeline.yml"]
2025-10-31 11:00:00 PDT
buildkite-agent: fatal: failed to read file: open .buildkite/smart_exhaustive_tests_pipeline.yml: no such file or directory
2025-10-31 11:00:00 PDT
🚨 Error: The command exited with status 1
2025-10-31 11:00:00 PDT
user command error: exit status 1
```<hr>This is an automatic backport of pull request #18386 done by [Mergify](https://mergify.com).

* feat(ci): support exhaustive tests for PRs (code changes or GH comment) (#18327)

* bk: fix regex and add new file (#18382)

* bk(smart exhaustive tests): tune the steps to support GH comments and changesets (#18383)

* chore: remove test file for exhaustive tests and normalise github commands (#18384)

---------

Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
(cherry picked from commit 906d5bd)

# Conflicts:
#	.buildkite/pull-requests.json
@mergify mergify Bot added backport conflicts Detected git conflicts labels Nov 1, 2025
@mergify mergify Bot added the conflicts Detected git conflicts label Nov 1, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Nov 1, 2025

Cherry-pick of 906d5bd has failed:

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

You are currently cherry-picking commit 906d5bd6.
  (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:
	new file:   .buildkite/smart_exhaustive_tests_pipeline.yml
	modified:   catalog-info.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/pull-requests.json

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Comment thread .buildkite/pull-requests.json Outdated
Comment thread .buildkite/pull-requests.json Outdated
Comment thread .buildkite/pull-requests.json Outdated
@v1v v1v removed the conflicts Detected git conflicts label Nov 2, 2025
@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

cc @donoghuc

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Nov 3, 2025

This pull request has not been merged yet. Could you please review and merge it @donoghuc? 🙏

@v1v v1v merged commit 559d279 into 8.19 Nov 3, 2025
7 checks passed
@v1v v1v deleted the mergify/bp/8.19/pr-18386 branch November 3, 2025 10:52
@donoghuc
Copy link
Copy Markdown
Member

donoghuc commented Nov 4, 2025

Thanks for resolving the merge conflict @v1v ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants