Skip to content

do not merge: debugging s390x flake#4198

Draft
Davo911 wants to merge 1 commit into
kubevirt:mainfrom
Davo911:s390x-job-debug
Draft

do not merge: debugging s390x flake#4198
Davo911 wants to merge 1 commit into
kubevirt:mainfrom
Davo911:s390x-job-debug

Conversation

@Davo911

@Davo911 Davo911 commented Jul 9, 2026

Copy link
Copy Markdown
Member

Seeing a lot of fails on that job lately, cannot reproduce it locally

What this PR does / why we need it:

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:

Release note:


Signed-off-by: Thomas-David Griedel griedel911@gmail.com
@kubevirt-prow

kubevirt-prow Bot commented Jul 9, 2026

Copy link
Copy Markdown

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

@kubevirt-prow

kubevirt-prow Bot commented Jul 9, 2026

Copy link
Copy Markdown

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@kubevirt-prow kubevirt-prow Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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 Jul 9, 2026
@kubevirt-prow

kubevirt-prow Bot commented Jul 9, 2026

Copy link
Copy Markdown

[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 mhenriks 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

@kubevirt-prow kubevirt-prow Bot added the size/M label Jul 9, 2026
@Davo911

Davo911 commented Jul 9, 2026

Copy link
Copy Markdown
Member Author

/test pull-containerized-data-importer-e2e-s390x

@kubevirt-prow

kubevirt-prow Bot commented Jul 9, 2026

Copy link
Copy Markdown

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

Test name Commit Details Required Rerun command
pull-containerized-data-importer-e2e-s390x 65ce0bc link false /test pull-containerized-data-importer-e2e-s390x
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.

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/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant