Closed chr15p closed 1 year ago
@chr15p: all tests passed!
Full PR test history. Your PR dashboard.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: chr15p, yevgeny-shnaidman
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@chr15p: This pull request references Jira Issue OCPBUGS-12520, which is invalid:
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.
/jira refresh
@chr15p: This pull request references Jira Issue OCPBUGS-12520, which is invalid:
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.
/jira refresh
@chr15p: This pull request references Jira Issue OCPBUGS-12520, which is invalid:
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.
@chr15p: This pull request references Jira Issue OCPBUGS-15096, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @wabouhamad
The bug has been updated to refer to the pull request using the external bug tracker.
sigh OCPBUGS-12520 does not target 4.13.0, it does targets 4.13.z but once openshift-ci-robot has looked at an issue it refuses to ever look at it again presumably because its catastrophically broken. The only work around is to raise a new issue and reference that instead so I created OCPBUGS-15096 to fix.
@chr15p Can you try to re-push? Seems like tide
changes aren't picked up for this PR.
@chr15p Can you try to re-push? Seems like
tide
changes aren't picked up for this PR.
@chr15p @ybettan no need for re-push, the tide changes are seen. All we need is staff-end-approve
@chr15p @ybettan no need for re-push, the tide changes are seen. All we need is staff-end-approve
You are right. I was still seeing the "tide: no branch..." error yesterday. Probably takes some time to propagate.
@chr15p: Jira Issue OCPBUGS-15096: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-15096 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
This PR has been included in build node-feature-discovery-container-v4.13.0-202311211131.p0.g79c2147.assembly.stream for distgit node-feature-discovery. All builds following this will include this PR.
cherry-pick 559405d46d07058a0edeab399074a7f4a989b1ad from master to backport the cve fix into release-4.13
Original commit message: move to golang.org/x/net v0.9.0 to fix https://github.com/advisories/GHSA-xrjj-mj9h-534m and https://github.com/advisories/GHSA-7m5q-w7p8-x8h4