802713 - Integrate mozpool into autophone

Status: RESOLVED WONTFIX

(Testing Graveyard :: Autophone, defect)

Description

[Mark Côté [:mcote]]

In preparation for shifting to a web service, we should first extract the pool elements and put them into separate objects. This will put into place most of the logic that autophone will need when the pool is moved entirely to a web service.

Comment 1

[Mark Côté [:mcote]]

Development of mozpool actually proceeded in the other direction, expanding from BlackMobileMagic.  So rather than extracting the pool elements from autophone, we'll be replacing them with mozpool.

Comment 2

[Mark Côté [:mcote]]

Further thinking 1.5 years later.  Mozpool may not buy us that much at this particular time.  While the separation of concerns would be nice, some important points are that

(a) Autophone runs all tests for each job on all devices.  It doesn't need to find a free device; it just queues each job up to run, eventually, on each device.  This means the top level of Mozpool (the request layer) is largely superfluous to Autophone.

(b) Autophone has had significant engineering effort spent in the last year to gracefully handle flaky devices.  While Mozpool's asynchronous state-machine approach is undoubtedly even more solid, the development effort to switch to that model is, at this time, probably not worth the cost, given that Autophone is very stable in its current configuration.

Comment 3

[Mark Côté [:mcote]]

Not an active goal; may be part of future investigations.

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

is this something we really want?  I don't know if mozpool is used by any project or even is still available/valid.

Comment 5

[Bob Clary [:bc] (inactive)]

Let's WONTFIX it and revisit if it ever comes up again.