bump aws job timeout to 3 hours#3712
Conversation
There was a problem hiding this comment.
This is something else, not e2e tests.
There was a problem hiding this comment.
ok i've removed that change.
There was a problem hiding this comment.
The other one is a launch-aws job too. More background on it here.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees 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 |
|
@bparees: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
|
I think this was solved in #3713, but I'll defer to @petr-muller |
|
Yeah, this sleep is unrelated to the timeouts we were seeing. Those were a result of an upstream serialization issue which caused the default 2h timeout override the prow-wide configured 4h timeout. The issue was ultimately resolved in #3713. /close |
|
/close |
|
@petr-muller: 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/test-infra repository. |
we appear to be consistently coming right up to the 2 hour timeout on the aws-serial job:
https://openshift-gce-devel.appspot.com/builds/origin-ci-test/pr-logs/directory/pull-ci-openshift-origin-master-e2e-aws-serial
i'd like to raise it to 3 hours to get through code freeze merges.
@smarterclayton @stevekuznetsov is this the right spot for this?