Skip to content

Conversation

@bpickard22
Copy link
Contributor

I added a new maketarget that skips some go building to allow us to run our upstream unit tests against downstream prs

cc @dougbtv @zshi-redhat

@openshift-ci openshift-ci bot requested review from maiqueb and pliurh November 26, 2024 21:51
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 26, 2024
@bpickard22
Copy link
Contributor Author

/hold need k8snetworkplumbingwg/whereabouts#516 to merge and then get downstream

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 26, 2024
@bpickard22
Copy link
Contributor Author

ci/prow/ordered-prow-config job is failing due some sanitation that needs to be ran related to other jobs, unrelated to whereabouts change

@bpickard22
Copy link
Contributor Author

ci/prow/ordered-prow-config job is failing due some sanitation that needs to be ran related to other jobs, unrelated to whereabouts change

I could include the changes here from running make jobs but i dont think that makes sense

@bpickard22
Copy link
Contributor Author

/hold-remove

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pr-rehearse

@zshi-redhat
Copy link
Contributor

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@bpickard22, pj-rehearse: unable to determine affected jobs ERROR:

could not load configuration from base revision of release repo: could not checkout worktree: '[git checkout 02888a96e57be1483a8395c3f76200d575a7f4cb]' failed with out:  and error exec: Stdout already set

If the problem persists, please contact Test Platform.

@openshift-ci-robot
Copy link
Contributor

@bpickard22, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from base revision of release repo: could not checkout worktree: '[git checkout 02888a96e57be1483a8395c3f76200d575a7f4cb]' failed with out:  and error exec: Stdout already set
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@bpickard22
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-whereabouts-cni-master-whereabouts-unit

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22

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

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@bpickard22: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-whereabouts-cni-main-whereabouts-unit openshift/whereabouts-cni presubmit Presubmit changed
pull-ci-openshift-whereabouts-cni-main-e2e-aws openshift/whereabouts-cni presubmit Ci-operator config changed
pull-ci-openshift-whereabouts-cni-main-images openshift/whereabouts-cni presubmit Ci-operator config changed
pull-ci-openshift-whereabouts-cni-main-okd-scos-e2e-aws-ovn openshift/whereabouts-cni presubmit Ci-operator config changed
pull-ci-openshift-whereabouts-cni-main-okd-scos-images openshift/whereabouts-cni presubmit Ci-operator config changed
pull-ci-openshift-whereabouts-cni-main-security openshift/whereabouts-cni presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@bpickard22
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bpickard22: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2024

@bpickard22: 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
ci/rehearse/openshift/whereabouts-cni/master/okd-scos-e2e-aws-ovn e73ceda link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-master-okd-scos-e2e-aws-ovn
ci/rehearse/openshift/whereabouts-cni/master/e2e-aws e73ceda link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-master-e2e-aws
ci/rehearse/openshift/whereabouts-cni/master/okd-scos-images e73ceda link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-master-okd-scos-images
ci/rehearse/openshift/whereabouts-cni/main/e2e-aws 81b3b49 link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-main-e2e-aws
ci/rehearse/openshift/whereabouts-cni/master/whereabouts-unit e73ceda link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-master-whereabouts-unit
ci/rehearse/openshift/whereabouts-cni/main/okd-scos-images 81b3b49 link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-main-okd-scos-images
ci/rehearse/openshift/whereabouts-cni/main/images 81b3b49 link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-main-images
ci/rehearse/openshift/whereabouts-cni/main/okd-scos-e2e-aws-ovn 81b3b49 link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-main-okd-scos-e2e-aws-ovn
ci/rehearse/openshift/whereabouts-cni/main/whereabouts-unit 81b3b49 link unknown /pj-rehearse pull-ci-openshift-whereabouts-cni-main-whereabouts-unit

Full PR test history. Your PR dashboard.

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.

@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 10, 2025
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 25, 2025
@bpickard22 bpickard22 changed the title Leverage new makefile target in whereabouts CORENET-688: Leverage new makefile target in whereabouts Mar 5, 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 Mar 5, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 5, 2025

@bpickard22: This pull request references CORENET-688 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

I added a new maketarget that skips some go building to allow us to run our upstream unit tests against downstream prs

cc @dougbtv @zshi-redhat

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.

@bpickard22
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 5, 2025

@bpickard22: This pull request references CORENET-688 which is a valid jira issue.

In response to this:

/jira refresh

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.

@bpickard22
Copy link
Contributor Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 5, 2025
@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 4, 2025
@bpickard22
Copy link
Contributor Author

/remove-lifecycle rotten

@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 30, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 30, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-bot
Copy link
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this May 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 15, 2025

@openshift-bot: Closed this PR.

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants