Skip to content

WIP - Setup prow for release-1.7-aie-nv#4966

Open
rthallisey wants to merge 1 commit into
kubevirt:mainfrom
rthallisey:prow-aie-1.7
Open

WIP - Setup prow for release-1.7-aie-nv#4966
rthallisey wants to merge 1 commit into
kubevirt:mainfrom
rthallisey:prow-aie-1.7

Conversation

@rthallisey

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Add Prow presubmit and postsubmit jobs for kubevirt/kubevirt-aie release-1.7-aie-nv branch.

    pull-kubevirt-aie-build-1.7-aie-nv
    pull-kubevirt-aie-build-arm64-1.7-aie-nv
    pull-kubevirt-aie-code-lint-1.7-aie-nv
    pull-kubevirt-aie-unit-test-1.7-aie-nv
    pull-kubevirt-aie-unit-test-arm64-1.7-aie-nv
    pull-kubevirt-aie-kind-1.35-sig-compute-arm64-1.7-aie-nv
    pull-kubevirt-aie-kind-1.35-conformance-arm64-1.7-aie-nv
    push-kubevirt-aie-virt-launcher-1.7-aie-nv

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

Release note:

NONE

@kubevirt-bot kubevirt-bot added the dco-signoff: no Indicates the PR's author has not DCO signed all their commits. label Apr 16, 2026
@kubevirt-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jean-edouard for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Signed-off-by: Ryan Hallisey <rhallisey@nvidia.com>
@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. and removed dco-signoff: no Indicates the PR's author has not DCO signed all their commits. labels Apr 16, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@dollierp

Copy link
Copy Markdown
Contributor

/rehearse pull-kubevirt-aie-build-1.7-aie-nv
/rehearse pull-kubevirt-aie-build-arm64-1.7-aie-nv
/rehearse pull-kubevirt-aie-code-lint-1.7-aie-nv
/rehearse pull-kubevirt-aie-unit-test-1.7-aie-nv
/rehearse pull-kubevirt-aie-unit-test-arm64-1.7-aie-nv
/rehearse pull-kubevirt-aie-kind-1.35-sig-compute-arm64-1.7-aie-nv
/rehearse pull-kubevirt-aie-kind-1.35-conformance-arm64-1.7-aie-nv

@kubevirt-bot

Copy link
Copy Markdown
Contributor

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-aie-kind-1.35-sig-compute-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-kind-1.35-conformance-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-build-1.7-aie-nv
rehearsal-pull-kubevirt-aie-build-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-code-lint-1.7-aie-nv
rehearsal-pull-kubevirt-aie-unit-test-1.7-aie-nv
rehearsal-pull-kubevirt-aie-unit-test-arm64-1.7-aie-nv
Further information on rehearsals

A rehearsal can be triggered for all jobs by commenting either /rehearse or /rehearse all on this PR.

A rehearsal for a specific job can be triggered by commenting /rehearse {job-name}.

Commenting /rehearse ? triggers a comment with a list of jobs that can be rehearsed.

A pull request can be rehearsed if either the user is authorized to rehearse or the pull
request has the ok-to-rehearse label.

Authorized users are the group of users that are members of the KubeVirt GitHub
organization AND either are approvers[1] for all files in the pull request or are
top-level approvers[1] in the project-infra project.

[1]: see OWNERS file definition for reference.

@kubevirt-bot

kubevirt-bot commented Apr 16, 2026

Copy link
Copy Markdown
Contributor

@rthallisey: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
rehearsal-pull-kubevirt-aie-kind-1.35-conformance-arm64-1.7-aie-nv 4b77a82 link false /test pull-kubevirt-aie-kind-1.35-conformance-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-kind-1.35-sig-compute-arm64-1.7-aie-nv 4b77a82 link true /test pull-kubevirt-aie-kind-1.35-sig-compute-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-unit-test-arm64-1.7-aie-nv 4b77a82 link true /test pull-kubevirt-aie-unit-test-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-build-arm64-1.7-aie-nv 4b77a82 link true /test pull-kubevirt-aie-build-arm64-1.7-aie-nv
rehearsal-pull-kubevirt-aie-build-1.7-aie-nv 4b77a82 link true /test pull-kubevirt-aie-build-1.7-aie-nv
rehearsal-pull-kubevirt-aie-unit-test-1.7-aie-nv 4b77a82 link true /test pull-kubevirt-aie-unit-test-1.7-aie-nv
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.

@rthallisey rthallisey changed the title Setup prow for release-1.7-aie-nv WIP - Setup prow for release-1.7-aie-nv Apr 20, 2026
@kubevirt-bot kubevirt-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 20, 2026
@kubevirt-bot

Copy link
Copy Markdown
Contributor

There has been no activity on this PR for 45 days.
To protect limited CI resources, it has been automatically labelled 'stale'.
This PR will automatically rot after an additional 14 days of inactivity, and will be closed shortly after that.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle stale
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants