Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NO-JIRA: denylist: snooze ostree.sync on s390x #1721

Merged
merged 1 commit into from
Jan 28, 2025
Merged

NO-JIRA: denylist: snooze ostree.sync on s390x #1721

merged 1 commit into from
Jan 28, 2025

Conversation

marmijo
Copy link
Contributor

@marmijo marmijo commented Jan 28, 2025

This test is failing intermittently on s390x. Let's snooze it for now to unblock the pipeline while we investigate:
#1720

@marmijo
denylist: snooze ostree.sync on s390x
757c4e0 
This test is failing intermittently on s390x. Let's snooze it for now
to unblock the pipeline while we investigate:
openshift#1720
@marmijo marmijo changed the title denylist: snooze ostree.sync on s390x NO-JIRA: denylist: snooze ostree.sync on s390x Jan 28, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 28, 2025
@openshift-ci-robot
Copy link

@marmijo: This pull request explicitly references no jira issue.

In response to this:

This test is failing intermittently on s390x. Let's snooze it for now to unblock the pipeline while we investigate:
#1720

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 28, 2025
dustymabe
dustymabe approved these changes Jan 28, 2025
View reviewed changes
Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

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

/lgtm

@dustymabe
Copy link
Member

skipping CI since it won't test this change

@dustymabe dustymabe merged commit bae5f3d into openshift:master Jan 28, 2025
3 of 12 checks passed
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustymabe, marmijo

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:

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

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

@dustymabe dustymabe dustymabe approved these changes

@ravanelli ravanelli Awaiting requested review from ravanelli

@yasminvalim yasminvalim Awaiting requested review from yasminvalim

Assignees

@dustymabe dustymabe

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@marmijo @openshift-ci-robot @dustymabe