[CI] fix benchmark docker name #17827
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
kaisecheng
added
backport-active-9
|
This pull request does not have a backport label. Could you fix it @kaisecheng? 🙏
|
|
I can't correlate CI errors with this change. How they turned into red? |
Are you asking about the ubi docker tests? https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/2117 That should be fixed separately with #17828 |
donoghuc
reviewed
Jul 16, 2025
| ;; | ||
| *) | ||
| echo "Unsupported architecture: $(uname -m)" | ||
| ;; |
donoghuc
reviewed
Jul 16, 2025
|
@Mergifyio backport 8.17 8.18 8.19 9.0 9.1 |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf)
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf)
This was referenced Jul 16, 2025
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf)
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf)
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf)
This was referenced Jul 16, 2025
kaisecheng
added a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf) Co-authored-by: kaisecheng <[email protected]>
kaisecheng
added a commit
that referenced
this pull request
Jul 16, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf) Co-authored-by: kaisecheng <[email protected]>
💛 Build succeeded, but was flaky
Failed CI StepsHistory
|
kaisecheng
added a commit
that referenced
this pull request
Jul 22, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf) Co-authored-by: kaisecheng <[email protected]>
kaisecheng
added a commit
that referenced
this pull request
Jul 22, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf) Co-authored-by: kaisecheng <[email protected]>
kaisecheng
added a commit
that referenced
this pull request
Jul 22, 2025
This commit uses standardize docker name for new versions (cherry picked from commit 198adcf) Co-authored-by: kaisecheng <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit uses standardize docker name for new versions