On Tue, Feb 21, 2012 at 09:02:16AM +1300, Michael Hudson-Doyle wrote: > On Mon, 20 Feb 2012 10:08:42 +0100, Alexander Sack <[email protected]> wrote: > > On Sat, Feb 18, 2012 at 5:42 PM, Dave Pigott <[email protected]> wrote: > > > > > Hi Paul, > > > > > > All cables in, just not installed. I started the installations on Tuesday, > > > but had to pick boards that were available. Didn't want to upgrade while > > > boards were running tests. I created an "audio-loopback" tag and > > > associated > > > with the boards that currently have it installed. Intend to start the > > > upgrade with the others on Monday. > > > > > > > Great. How to set requirement tags for jobs submitted? Is this something we > > can do inside the test definition? Or is this decided by the job submitter > > atm? > > It's done in the job submission. "device_tags": ["audio-loopback"] is > the syntax to use.
This does raise an interesting question. Perhaps test definitions could require certain tags and then the scheduler could automatically assemble the superset of required tags. I guess it depends on why we want to use tags: 1) Because the test will fail on devices without them 2) Because we want to anrrow the possible selection of devices. Best regards ZK _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
