Hi Johnatan,
Can you confirm one more thing for me? Can you actually see the metadata you provided on the job results page in the collapsable "Metadata" menu (i.e. https://staging.validation.linaro.org/results/196825)
Thanks, Stevan
On 11/03/2017 01:27 PM, Jonathan Guyot wrote:
Thanks Stevan for replying,
I have just made a test on a lava-server from the stretch debian backports, and I observe the same issue.
The X-axis attribute seems to be accepted when I set it, and a new row appears on my chart with the name "jenkins-build", and I can see an table with 2 rows headers but no datas : _______________ | | | *Date* | |_______________| | | | jenkins-build | |_______________|
… and that's it.
The table I get contains only this, and the results of my query are not shown in the chart's table.
I use the version 2017.7 of lava.
I wonder what is going on for now. The X-axis attribute I select is in the metadatas of the job as explained in my previous mail.
Jonathan
Le ven. 3 nov. 2017 à 11:46, Stevan Radakovic <stevan.radakovic@linaro.org mailto:stevan.radakovic@linaro.org> a écrit :
Hi Jonathan, In that version of LAVA server, the x-axis field is looking in the old legacy data related to V1. There's a patch which fixes that: https://git.linaro.org/lava/lava-server.git/commit/?id=0f2d8a4ff4cf0fb18dbb73578c613cb62d2891df However, it's only been released in 2017.04 and later builds. HTH. Thanks, Stevan On 11/03/2017 10:00 AM, Jonathan Guyot wrote:Hello everybody, I am working with both Jenkins and lava and I thought it was possible to change X attributes in charts to use Jenkins build number instead of a date. In my job, I defined a metadata like this : job_name: quad-ssh-host device_type: ssh *metadata: {jenkins-build: 725, job-context: nightly}* timeouts: job: minutes: 10 action: minutes: 3 connection: seconds: 20 visibility: public […] and I made a query that can select these jobs using job-context as a filter. Then, in the chart, I wanted to use the jenkins-build value to group job instead of a simple date, but the chart does not seem to be able to do that. I made many tries on the lava 2017.2 version. I wonder whether I am misusing lava charts or if it is an issue that need a fix. Thanks in advance for any reply. Jonathan _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org <mailto:Lava-users@lists.linaro.org> https://lists.linaro.org/mailman/listinfo/lava-users-- Stevan Radaković | LAVA Engineer Linaro.org <www.linaro.org <http://www.linaro.org>> │ Open source software for ARM SoCs _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org <mailto:Lava-users@lists.linaro.org> https://lists.linaro.org/mailman/listinfo/lava-users