Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jrvaldes
Copy link
Contributor

@jrvaldes jrvaldes commented Jan 10, 2023

This is a manual cherry-pick of #6505

None

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2023

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

@openshift-ci openshift-ci bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jan 10, 2023
@codecov
Copy link

codecov bot commented Jan 10, 2023

Codecov Report

Merging #6506 (484e267) into release-1.24 (ae53655) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-1.24    #6506   +/-   ##
=============================================
  Coverage         42.91%   42.92%           
=============================================
  Files               124      124           
  Lines             12741    12741           
=============================================
+ Hits               5468     5469    +1     
+ Misses             6749     6748    -1     
  Partials            524      524           


// SpecAddMount adds a specified mount to the spec
//
//nolint:gocritic // passing the spec mount around here is intentional
Copy link

Choose a reason for hiding this comment

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

nolintlint: directive //nolint:gocritic // passing the spec mount around here is intentional is unused for linter "gocritic"


ℹ️ Learn about @sonatype-lift commands

You can reply with the following commands. For example, reply with @sonatype-lift ignoreall to leave out all findings.

Command Usage
@sonatype-lift ignore Leave out the above finding from this PR
@sonatype-lift ignoreall Leave out all the existing findings from this PR
@sonatype-lift exclude <file|issue|path|tool> Exclude specified file|issue|path|tool from Lift findings by updating your config.toml file

Note: When talking to LiftBot, you need to refresh the page to see its response.
Click here to add LiftBot to another repo.


Was this a good recommendation?
[ 🙁 Not relevant ] - [ 😕 Won't fix ] - [ 😑 Not critical, will fix ] - [ 🙂 Critical, will fix ] - [ 😊 Critical, fixing now ]

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@cri-o/cri-o-maintainers I may need directions here; Is this required in release-1.24? sonatype-lift bot did not complain in 1.25 or 1.26 PRs.

Copy link
Member

Choose a reason for hiding this comment

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

it's possible we'd not enabled the gocritic linter here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed the unused linter instructions in 484e267

@jrvaldes jrvaldes changed the title [release-1.24] Fix GitHub actions CI [release-1.24] OCPBUGS-3708: Fix GitHub actions CI Jan 10, 2023
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 10, 2023
@openshift-ci-robot
Copy link

@jrvaldes: This pull request references Jira Issue OCPBUGS-3708, which is invalid:

  • expected Jira Issue OCPBUGS-3708 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is a manual cherry-pick of #6505

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/test-infra repository.

@jrvaldes jrvaldes changed the title [release-1.24] OCPBUGS-3708: Fix GitHub actions CI [release-1.24] Fix GitHub actions CI Jan 10, 2023
@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 10, 2023
@openshift-ci-robot
Copy link

@jrvaldes: No Jira bug is referenced in the title of this pull request.
To reference a bug, add 'OCPBUGS-XXX:' to the title of this pull request and request another bug refresh with /jira refresh.

Details

In response to this:

This is a manual cherry-pick of #6505

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/test-infra repository.

@jrvaldes jrvaldes force-pushed the cherry-pick-6392-to-release-1.24 branch from 07a619c to 3a1fa33 Compare January 10, 2023 15:13
Signed-off-by: Sascha Grunert <[email protected]>
(cherry picked from commit 51d3621)
@jrvaldes jrvaldes force-pushed the cherry-pick-6392-to-release-1.24 branch from 3a1fa33 to 484e267 Compare January 10, 2023 15:14
@jrvaldes jrvaldes marked this pull request as ready for review January 10, 2023 15:15
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 10, 2023
@openshift-ci openshift-ci bot requested review from QiWang19 and klihub January 10, 2023 15:16
@haircommander
Copy link
Member

/approve

LGTM, thanks!

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, jrvaldes

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 Jan 10, 2023
@haircommander
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. labels Jan 10, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Jan 10, 2023
@jrvaldes
Copy link
Contributor Author

Set release-note as None in the PR description as per release note process

@openshift-merge-robot openshift-merge-robot merged commit 1d7361a into cri-o:release-1.24 Jan 10, 2023
@jrvaldes
Copy link
Contributor Author

/cherry-pick release-1.23

@openshift-cherrypick-robot

@jrvaldes: #6506 failed to apply on top of branch "release-1.23":

Applying: Fix GitHub actions CI
Using index info to reconstruct a base tree...
M	.github/workflows/test.yml
M	.github/workflows/verify.yml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/verify.yml
CONFLICT (content): Merge conflict in .github/workflows/verify.yml
Auto-merging .github/workflows/test.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix GitHub actions CI
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-1.23

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/test-infra 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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants