On Tue, 24 Jul 2018 at 14:35, Hemanth K V kv.hemanth.mys@gmail.com wrote:
Hello Lava Users,
We are creating queries in LAVA and adding multiple conditions to query.For example in our yaml job definition we have included os field in metadata section which will have different values.For example following is the metadata section for 2 different jobs
Job1:
metadata: description: '"Build SiemensIPC-327E target with latest build"' os: Debian device: imx6q Build_ID: QA-BUILD-F0150
Job2: metadata: description: '"Build SiemensIPC-327E target with latest build"' os: Ubuntu device: imx6q Build_ID: QA-BUILD-F0150
Now with queries I am trying to just filter out job running with Build_ID( QA-BUILD-F0150 ) and on only os debian.
Entity Field Operator Value
namedtestattribute Build_ID exact QA-BUILD-F0150
namedtestattribute os
exact Debian
When I am creating queries with above information, as a user when I run the query the query results will just list Job1 information but at present in LAVA both the jobs are getting listed. Is this the expected behavior?The LAVA server version used is 2018.5.post1 release.
Is this a live query or the default cached query? If default, when was the query last refreshed?
You can also turn a saved query into a URL and see what matches by editing the query string.
For example: https://staging.validation.linaro.org/results/query/+custom?entity=testsuite...
You may want to switch to Contains rather than exact
Incidentally, when describing a Query, using the URL makes it much clearer to everyone what the query is trying to do. Just click on Results and This query by URL. This allows queries to be directly compared in text.
Thanks, Hemanth.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users