"Informational" Tast tests currently run as part of bvt-perbuild. With the way that suites are currently scheduled, this means that they won't run if bvt-installer fails (see  issue 910952 ).

Per discussion with ihf@, I'm planning to move these tests (which are executed by the tast.informational-{android,chrome,system} Autotest server tests) into a new bvt-tast-informational suite.

I'll make this suite start earlier so that it'll run even if bvt-installer fails. It should still run asynchronously.