Decrease global timeouts from 6h to 2h

Description

The timeout is currently 6h, this was needed back when we had very long upgrade jobs.

We should probably decrease it to 2h, or maybe even less. Most stuff we have these days shouldn't be running more then ~40m.

Activity

Show:

Barak Korren June 24, 2018 at 7:55 AM

This ticket talked about STDCI V1. In V2 timeout is already 2h per-thread.

Not going to do this for v1 any more.

Barak Korren August 16, 2017 at 2:33 PM

See my tickets for example on how to link ticket to Jira so its easy to find it during team meeting.

As noted, the OST check-patch jobs currently run for a long time, we need to look at the trend and see how long to consider to what we can shorten the timeout.

Dafna Ron August 16, 2017 at 11:11 AM

Dafna Ron August 13, 2017 at 4:34 PM

can you please give more info on the task?
looking Jenkins global settings I can see there are several timeout fields and none are 6h so I am not sure I am looking at the correct location or if the fields I am looking at are not correct?

Won't Fix

Details

Assignee

Reporter

Priority

Created June 1, 2017 at 7:33 AM
Updated September 2, 2018 at 3:50 PM
Resolved June 24, 2018 at 7:55 AM