WINC-1383: Bump use-trusted-artifact step memory

[sebsoto]

This step is the one in particular that is going OOM. Only it should be given the memory increase.

[openshift-ci-robot]

@sebsoto: This pull request references WINC-1383 which is a valid jira issue.

In response to this:

This step is the one in particular that is going OOM. Only it should be given the memory increase.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[wgahnagl]

/lgtm

build-source-image was also going oom, but that's not getting changed here 👍
Just don't want to forget that it used to

[jrvaldes]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, mansikulkarni96, sebsoto

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mansikulkarni96,sebsoto]

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

[sebsoto]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.19

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.

[sebsoto]

/cherry-pick release-4.18

[sebsoto]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

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.

[sebsoto]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

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.

[sebsoto]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

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.

[sebsoto]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

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.

[sebsoto]

/override ci/prow/images ci/prow/ci-bundle-wmco-bundle

[openshift-ci]

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/ci-bundle-wmco-bundle, ci/prow/images

In response to this:

/override ci/prow/images ci/prow/ci-bundle-wmco-bundle

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]

@sebsoto: #2833 failed to apply on top of branch "release-4.14":

Applying: Bump use-trusted-artifact step memory
Using index info to reconstruct a base tree...
A	.tekton/windows-machine-config-operator-bundle-master-pull-request.yaml
A	.tekton/windows-machine-config-operator-bundle-master-push.yaml
A	.tekton/windows-machine-config-operator-master-pull-request.yaml
A	.tekton/windows-machine-config-operator-master-push.yaml
Falling back to patching base and 3-way merge...
Auto-merging .tekton/windows-machine-config-operator-release-4-14-push.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-release-4-14-push.yaml
Auto-merging .tekton/windows-machine-config-operator-release-4-14-pull-request.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-release-4-14-pull-request.yaml
Auto-merging .tekton/windows-machine-config-operator-bundle-release-4-14-push.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-bundle-release-4-14-push.yaml
Auto-merging .tekton/windows-machine-config-operator-bundle-release-4-14-pull-request.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-bundle-release-4-14-pull-request.yaml
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 Bump use-trusted-artifact step memory

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.

[openshift-ci]

@sebsoto: all tests passed!

Full PR test history. Your PR dashboard.

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-cherrypick-robot]

@sebsoto: new pull request created: #2836

In response to this:

/cherry-pick release-4.19

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]

@sebsoto: new pull request created: #2837

In response to this:

/cherry-pick release-4.18

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]

@sebsoto: new pull request created: #2838

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.

[openshift-cherrypick-robot]

@sebsoto: new pull request created: #2839

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.

[openshift-cherrypick-robot]

@sebsoto: #2833 failed to apply on top of branch "release-4.15":

Applying: Bump use-trusted-artifact step memory
Using index info to reconstruct a base tree...
A	.tekton/windows-machine-config-operator-bundle-master-pull-request.yaml
A	.tekton/windows-machine-config-operator-bundle-master-push.yaml
A	.tekton/windows-machine-config-operator-master-pull-request.yaml
A	.tekton/windows-machine-config-operator-master-push.yaml
Falling back to patching base and 3-way merge...
Auto-merging .tekton/windows-machine-config-operator-release-4-15-push.yaml
Auto-merging .tekton/windows-machine-config-operator-release-4-15-pull-request.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-release-4-15-pull-request.yaml
Auto-merging .tekton/windows-machine-config-operator-bundle-release-4-15-push.yaml
Auto-merging .tekton/windows-machine-config-operator-bundle-release-4-15-pull-request.yaml
CONFLICT (content): Merge conflict in .tekton/windows-machine-config-operator-bundle-release-4-15-pull-request.yaml
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 Bump use-trusted-artifact step memory

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.