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.
Thanks, Hemanth.
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
Thanks Neil for detailed explanation.We are trying with default cached query which we are refreshing periodically.
results/query/+custom?entity=testjob&conditions=namedtestattribute__product__icontains__Debian,namedtestattribute__build__icontains__build10#
For example Now if above is the query ,in which we are having 2 conditions of namedtestattribute will LAVA list only the jobs having both metadata values "Debian and build 10" or will LAVA list all jobs in which either of metadata "Debian and build10" is available.
Thanks, Hemanth.
On Tue, Jul 24, 2018 at 7:37 PM, Neil Williams neil.williams@linaro.org wrote:
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&conditions=namedtestattribute_ _path__icontains__lxc-server-stretch.yaml,testsuite__name__ icontains__0_server-unittests-stretch
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
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On Wed, 25 Jul 2018 at 07:48, Hemanth K V kv.hemanth.mys@gmail.com wrote:
Thanks Neil for detailed explanation.We are trying with default cached query which we are refreshing periodically.
results/query/+custom?entity=testjob&conditions=namedtestattribute__product__icontains__Debian,namedtestattribute__build__icontains__build10#
For example Now if above is the query ,in which we are having 2 conditions of namedtestattribute will LAVA list only the jobs having both metadata values "Debian and build 10" or will LAVA list all jobs in which either of metadata "Debian and build10" is available.
Results need to match all criteria in the Query to be displayed.
Thanks, Hemanth.
On Tue, Jul 24, 2018 at 7:37 PM, Neil Williams neil.williams@linaro.org wrote:
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
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Hello Neil,
Results are matching to any criteria in the Query.
If the following is the metadata of Jobs Job1: metadata: OS: Ubuntu Build_ID: QA-BUILD-F0153
Job2: metadata: OS: Debian Build_ID: QA-BUILD-F0153
Job3: metadata: OS: Debian Build_ID: QA-BUILD-F0153
When we are creating following query then the query results lists all the 3 jobs having above metadata.
results/query/+custom?entity=testjob&conditions=namedtestattribute__os__icontains__Debian,namedtestattribute__Build_ID__icontains__QA-BUILD-F0153
Let me know if I am making any mistake here.What I am expecting is LAVA should list only Job2 and Job 3. The LAVA server version used is 2018.5.post1 release.
Thanks, Hemanth.
On Wed, Jul 25, 2018 at 12:22 PM, Neil Williams neil.williams@linaro.org wrote:
On Wed, 25 Jul 2018 at 07:48, Hemanth K V kv.hemanth.mys@gmail.com wrote:
Thanks Neil for detailed explanation.We are trying with default cached query which we are refreshing periodically.
results/query/+custom?entity=testjob&conditions= namedtestattribute__product__icontains__Debian, namedtestattribute__build__icontains__build10#
For example Now if above is the query ,in which we are having 2 conditions of namedtestattribute will LAVA list only the jobs having both metadata values "Debian and build 10" or will LAVA list all jobs in which either of metadata "Debian and build10" is available.
Results need to match all criteria in the Query to be displayed.
Thanks, Hemanth.
On Tue, Jul 24, 2018 at 7:37 PM, Neil Williams neil.williams@linaro.org wrote:
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&conditions=namedtestattribute_ _path__icontains__lxc-server-stretch.yaml,testsuite__name__ icontains__0_server-unittests-stretch
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
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On Wed, 25 Jul 2018 at 08:38, Hemanth K V kv.hemanth.mys@gmail.com wrote:
Hello Neil,
Results are matching to any criteria in the Query.
If the following is the metadata of Jobs Job1: metadata: OS: Ubuntu Build_ID: QA-BUILD-F0153
Job2: metadata: OS: Debian Build_ID: QA-BUILD-F0153
Job3: metadata: OS: Debian Build_ID: QA-BUILD-F0153
When we are creating following query then the query results lists all the 3 jobs having above metadata.
results/query/+custom?entity=testjob&conditions=namedtestattribute__os__icontains__Debian,namedtestattribute__Build_ID__icontains__QA-BUILD-F0153
Let me know if I am making any mistake here.What I am expecting is LAVA should list only Job2 and Job 3. The LAVA server version used is 2018.5.post1 release.
OK, this could be a bug when a Query uses multiple metadata test conditions rather than a mix of metadata and testjob/testsuite conditions.
I've created https://projects.linaro.org/browse/LAVA-1385 to work on a fix.
Thanks, Hemanth.
On Wed, Jul 25, 2018 at 12:22 PM, Neil Williams neil.williams@linaro.org wrote:
On Wed, 25 Jul 2018 at 07:48, Hemanth K V kv.hemanth.mys@gmail.com wrote:
Thanks Neil for detailed explanation.We are trying with default cached query which we are refreshing periodically.
results/query/+custom?entity=testjob&conditions=namedtestattribute__product__icontains__Debian,namedtestattribute__build__icontains__build10#
For example Now if above is the query ,in which we are having 2 conditions of namedtestattribute will LAVA list only the jobs having both metadata values "Debian and build 10" or will LAVA list all jobs in which either of metadata "Debian and build10" is available.
Results need to match all criteria in the Query to be displayed.
Thanks, Hemanth.
On Tue, Jul 24, 2018 at 7:37 PM, Neil Williams <neil.williams@linaro.org
wrote:
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
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
lava-users@lists.lavasoftware.org
-
Hemanth K V -
Neil Williams