increase gcp-ovn-rt-upgrade timeout from 5h->6h#69287
Conversation
|
can you run the job a few times here so we can see the effect of your changes and see if it passes? |
|
/pj-reherse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade |
1 similar comment
|
/pj-reherse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade |
|
doesnt seem to be working jamo |
|
/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade |
|
@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
it's working now. pj-rehearse likes to ignore you sometimes. :( but I think we should |
|
we can abandon this jamo i think - we saw something in the logs: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1758716716570649?thread_ts=1758647063.563739&cid=C01CQA76KMX |
/close |
|
@jluhrsen: Closed this PR. DetailsIn response to this:
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. |
|
/reopen |
|
@martinkennelly: Reopened this PR. DetailsIn response to this:
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. |
|
@jluhrsen I looked at this job and i think your instincts/analysis were right originally... it does look at the job and it passes the tests after 3 hours but then hits the timeout sometimes. I dont see any other issues.... so it does just look like things are just taking longer and then timing out... |
|
/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade |
|
@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@martinkennelly: job(s): pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade either don't exist or were not found to be affected, and cannot be rehearsed |
f2517de to
613f069
Compare
|
/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade |
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade |
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm TYSM jamo.. |
|
@jluhrsen can you give your reasoning for including the job |
44708b8 to
70b5881
Compare
@martinkennelly , I have fat fingers I guess. unintentional. fixed. need the labels back pls |
|
@jluhrsen: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@jluhrsen generated config job isn't happy. |
|
/hold until generated config is good |
it some times will go past 5h and fails, even though its working on post steps and the actual e2e part has passed on major factor for these specific jobs is that the build time for OVNK presubmits can take 30-60+ minutes just to build the PR before the job can even start the process of starting a cluster to run the e2e. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
70b5881 to
6b120d9
Compare
@martinkennelly should be good now. forgot to run the |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jluhrsen, martinkennelly The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/rehearsals-ack |
|
/rehearse ack |
|
@jluhrsen can you ack rehearsals? We've already verified it. |
|
/pj-rehearse ack |
|
@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/unhold |
it some times will go past 5h and fails, even though its working on post steps and the actual e2e part has passed