Skip to content

USHIFT-2987: Add support for low-latency feature#3769

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
agullon:USHIFT-2987
Aug 15, 2024
Merged

USHIFT-2987: Add support for low-latency feature#3769
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
agullon:USHIFT-2987

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Aug 14, 2024

Which issue(s) this PR addresses:

Closes #

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 14, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 14, 2024

@agullon: This pull request references USHIFT-2987 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 August 14, 2024 18:14
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 15, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 15, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1dfe3bd and 2 for PR HEAD b4594c9 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2024

@agullon: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit ba3b670 into openshift:main Aug 15, 2024
@agullon
Copy link
Contributor Author

agullon commented Sep 10, 2024

/cherry-pick release-4.17

@openshift-cherrypick-robot

@agullon: new pull request created: #3893

Details

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@agullon
Copy link
Contributor Author

agullon commented Nov 12, 2024

/cherry-pick release-4.17

@openshift-cherrypick-robot

@agullon: new pull request created: #4170

Details

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@agullon
Copy link
Contributor Author

agullon commented Feb 12, 2025

/cherry-pick release-4.16

@openshift-cherrypick-robot

@agullon: new pull request created: #4540

Details

In response to this:

/cherry-pick release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@agullon
Copy link
Contributor Author

agullon commented Feb 12, 2025

/cherry-pick release-4.15

@agullon
Copy link
Contributor Author

agullon commented Feb 12, 2025

/cherry-pick release-4.14

@openshift-cherrypick-robot

@agullon: #3769 failed to apply on top of branch "release-4.15":

Applying: add support for low--latency
Using index info to reconstruct a base tree...
M	test/run.sh
Falling back to patching base and 3-way merge...
Auto-merging test/run.sh
CONFLICT (content): Merge conflict in test/run.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 add support for low--latency

Details

In response to this:

/cherry-pick release-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@agullon: #3769 failed to apply on top of branch "release-4.14":

Applying: add support for low--latency
Using index info to reconstruct a base tree...
M	test/run.sh
Falling back to patching base and 3-way merge...
Auto-merging test/run.sh
CONFLICT (content): Merge conflict in test/run.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 add support for low--latency

Details

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants