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.

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

Cirrus: Reduce APIv2 task timeout #11372

Merged
merged 1 commit into from
Aug 31, 2021

Conversation

cevich
Copy link
Member

@cevich cevich commented Aug 31, 2021

At the time of this commit, a significant problem has been identified
(introduced in f5ce02b). The effect is, podman pull has a chance
of hanging, especially when re-pulling an existing image. While a fix
is in the works, there's no reason to make developers wait the full
(default) 1-hour timeout for the APIv2 task. Reduce it to 2x nominal
test runtime, so if the hang/flake is hit, the task can be re-run more
quickly.

Signed-off-by: Chris Evich [email protected]

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 31, 2021
@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

Note: The 10-minute runtime is a total guess based on my own memory/experience. It would be nice to confirm 20-minute timeout actually gives enough margin.

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

LGTM assuming 20 minutes give enough time.

Independent of the current flake, it makes sense 👍

@edsantiago
Copy link
Member

LGTM

@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

update: I peeped at around a dozen recent runs across several branches. The worst-case for this task completing is just over 7-minutes. So the 20m timeout is probably fine, considering some margin for new tests and the odd-ball infrastructure slowdowns.

@mheon
Copy link
Member

mheon commented Aug 31, 2021

/lgtm
/hold

@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 Aug 31, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2021
@cevich cevich changed the title [WIP] Cirrus: Reduce APIv2 task timeout Cirrus: Reduce APIv2 task timeout Aug 31, 2021
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 31, 2021
@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

Ahh, lovely, see there, flake happened and proves 20-minute time is helpful 😁
https://cirrus-ci.com/task/5621331594051584

@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

Oof, this task fails a lot. I see somebody else is helping me smash the re-run button, thanks 😁

@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

sigh more smashing the re-run button. I feel REALLY bad for all the other in-flight PRs right now, all waiting an hour 😢

Maybe should I make this a [CI:DOCS] or someone just merges it by force?

@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

@baude @edsantiago @vrothberg would you be okay if we just merge this w/o passing tests? I've re-run the APIv2 test 9-times now. Every time I press re-run after 20-minutes, I sympathize with literally everybody else who has to wait a hour 😓

@mheon
Copy link
Member

mheon commented Aug 31, 2021

Did you rebase on top of main? We should have a fix for the APIv2 issue landed.

@edsantiago
Copy link
Member

Aw. I was having so much fun pressing re-run.

At the time of this commit, a significant problem has been identified
(introduced in f5ce02b).  The effect is, `podman pull` has a chance
of hanging, especially when re-pulling an existing image.  While a fix
is in the works, there's no reason to make developers wait the full
(default) 1-hour timeout for the APIv2 task.  Reduce it to 2x nominal
test runtime, so if the hang/flake is hit, the task can be re-run more
quickly.

Signed-off-by: Chris Evich <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2021
@cevich
Copy link
Member Author

cevich commented Aug 31, 2021

Did you rebase on top of main? We should have a fix for the APIv2 issue landed.

Hmmm, well crap, I was hoping for more of a party-balloons and confetti event. Okay, there we go, it's rebased now.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, edsantiago

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2021
@edsantiago
Copy link
Member

/lgtm
/hold

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2021
@edsantiago
Copy link
Member

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 31, 2021
@openshift-merge-robot openshift-merge-robot merged commit dc2a3e3 into containers:main Aug 31, 2021
@cevich cevich deleted the apiv2_update branch April 18, 2023 14:45
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 31, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants