On Mon, 20 Feb 2012 20:30:23 +0000, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
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 asac@linaro.org wrote:
On Sat, Feb 18, 2012 at 5:42 PM, Dave Pigott dave.pigott@linaro.org 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.
Well, the scheduler doesn't know anything about the tests currently... I guess this is another thing that could change, or we could add some kind of nice interface for building job definition files that does know about tests. In general I like having a the job json as a low-level thing that we can pass around to very explicitly describe a job but that doesn't mean it's how our users should see a job.
Cheers, mwh