Skip to content

Revisit deployment timeouts introduced to mitigate problems from 110016 #11732

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
Open
soltysh opened this issue Nov 2, 2016 · 4 comments
Open

Revisit deployment timeouts introduced to mitigate problems from 110016 #11732

soltysh opened this issue Nov 2, 2016 · 4 comments
Assignees
@mfojtik
Labels
area/techdebt area/tests component/apps lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2

Comments

@soltysh
Copy link
Contributor

soltysh commented Nov 2, 2016

As part of struggling with #11016 we've increased timeouts in extended deployments tests. We should revisit those times when the aforementioned issue is fixed.
@soltysh soltysh added this to the 1.5.0 milestone Nov 2, 2016
@soltysh
Copy link
Contributor Author

soltysh commented Nov 2, 2016

#11729 is one example

@soltysh soltysh mentioned this issue Nov 2, 2016
Merged
@soltysh
Copy link
Contributor Author

soltysh commented Nov 2, 2016

@liggitt fyi

@0xmichalis 0xmichalis removed this from the 1.5.0 milestone Dec 2, 2016
@0xmichalis 0xmichalis assigned mfojtik and unassigned 0xmichalis Jan 30, 2017
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 8, 2018
@soltysh
Copy link
Contributor Author

soltysh commented Feb 13, 2018

/lifecycle frozen
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mfojtik mfojtik

Labels
area/techdebt area/tests component/apps lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mfojtik @soltysh @openshift-bot @0xmichalis @pweil- @openshift-ci-robot