422725 - Teach Talos how to cope with virus-scan lag

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Spun off from bug 421917 comment #3 (and onwards). Talos currently expects builds to be available on the ftp as soon tinderbox says they're done. Virus scanning could add up to 10 mins lag (SWAG), so we need to to some sort of test for file existence before firing the change. Or make the slave poll for the file, up to some timeout.

Comment 1

[Rob Campbell [:rc] (:robcee)]

we've had a 5 minute treeStableTimer on these before. Would bumping that up to a sufficiently high number fit the bill?

Comment 2

[Rob Campbell [:rc] (:robcee)]

Trying this tomorrow morning at 6am PDT.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Wasn't there some concern about making the race condition worse if treeStableTimer is increased ? My understanding is that we're doing bug 421917 tomorrow, and builds for talos will be dodging the scan lag until we resolve this bug.

Comment 4

[Rob Campbell [:rc] (:robcee)]

I was going to bump the timer along with 421917 but will hold off until we have a better solution.

Comment 5

[alice nodelman [:alice] [:anode]]

Talos is now directly notified of available builds by the builders themselves using sendchange.  I no longer believe that this lag is an issue, please re-open if it still exists.

Comment 6

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.