error-report-web django-nvd3 version
Hi,
can you be more specific about django-nvd3 version required by error-report-web?
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/tree/README
with 0.6.* it was complaining about missing kw_args param in load_chart calls, older versions were complaining about other changes.
I'm testing it (currently without graphs) in order to extend it to collect some build metrics and statistics from our builds (like every jenkins build and very local
developer build will upload back description of HW, build times and
other metrics so we can better evaluate icecc, sstate reuse ratio etc).
If something like that would be useful for upstream I can eventually contribute it back.
I've also updated the .bbclass to read all "configuration" from bb data and to upload the report after every build (sort of like tinderbox, oestats bbclass worked), that way is easier for us to globally enable it for all builds in our distro config without any interaction from developers.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Hi Martin,
Quoted 6 lines · On Thursday 06 March 2014 02:31:31 Martin Jansa wrote:
can you be more specific about django-nvd3 version required by error-report-web?
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/tree/READMEwith 0.6.* it was complaining about missing
kw_argsparam inload_chartcalls, older versions were complaining about other changes.
I'm not sure of the original version, but FWIW I did make a fix for this problem with 0.6 in the layer index the other day that might be useful as a reference:
As you can see I found I needed to update the d3/nvd3 js files at the same time.
Quoted 8 lines
I'm testing it (currently without graphs) in order to extend it to collect some build metrics and statistics from our builds (like every jenkins build and very local developer build will upload back description of HW, build times and other metrics so we can better evaluate icecc, sstate reuse ratio etc).
If something like that would be useful for upstream I can eventually contribute it back.
Seems reasonable to me, as long as it doesn't get in the way of handling error reports.
Quoted 5 lines
I've also updated the .bbclass to read all "configuration" from bb data and to upload the report after every build (sort of like tinderbox, oestats bbclass worked), that way is easier for us to globally enable it for all builds in our distro config without any interaction from developers.
As long as this is an option and not on by default (and ideally make it a trinary switch so you can decide to send just errors automatically) this should be OK also. Showing some kind of notification that it's doing it would be a good thing as well I think.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Hi Martin,
I should have been more specific about the versions, sorry. I've updated the README, it needs django-nvd3 0.1.11 and python-nvd3 0.6.0.
I usually install those on my Ubuntu host using pip.
Regards,
Andreea
-----Original Message-----
From: Martin Jansa [mailto:[email protected]]
Sent: Thursday, March 06, 2014 3:32 AM
To: Proca, Andreea B
Cc: [email protected]
Subject: error-report-web django-nvd3 version
Hi,
can you be more specific about django-nvd3 version required by error-report-web?
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/tree/README
with 0.6.* it was complaining about missing kw_args param in load_chart calls, older versions were complaining about other changes.
I'm testing it (currently without graphs) in order to extend it to collect some build metrics and statistics from our builds (like every jenkins build and very local developer build will upload back description of HW, build times and other metrics so we can better evaluate icecc, sstate reuse ratio etc).
If something like that would be useful for upstream I can eventually contribute it back.
I've also updated the .bbclass to read all "configuration" from bb data and to upload the report after every build (sort of like tinderbox, oestats bbclass worked), that way is easier for us to globally enable it for all builds in our distro config without any interaction from developers.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 6 lines · Andreea B
Hi Martin,
I should have been more specific about the versions, sorry. I've updated the README, it needs django-nvd3 0.1.11 and python-nvd3 0.6.0.
I usually install those on my Ubuntu host using pip.
Thank you, I didn't go that far into django-nvd3 history to try 0.1.11 version :).
I've small fix to make it compatible with 0.6.0, but I'll first try it with 0.1.11 to see if it's supposed to look like this.
Thank you very much for this project it came in right time for me :).
Quoted 22 lines
-----Original Message-----
From: Martin Jansa [mailto:[email protected]]
Sent: Thursday, March 06, 2014 3:32 AM
To: Proca, Andreea B
Cc: [email protected]
Subject: error-report-web django-nvd3 versionHi,
can you be more specific about django-nvd3 version required by error-report-web?
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/tree/READMEwith 0.6.* it was complaining about missing
kw_argsparam inload_chartcalls, older versions were complaining about other changes.I'm testing it (currently without graphs) in order to extend it to collect some build metrics and statistics from our builds (like every jenkins build and very local developer build will upload back description of HW, build times and other metrics so we can better evaluate icecc, sstate reuse ratio etc).
If something like that would be useful for upstream I can eventually contribute it back.
I've also updated the .bbclass to read all "configuration" from bb data and to upload the report after every build (sort of like tinderbox, oestats bbclass worked), that way is easier for us to globally enable it for all builds in our distro config without any interaction from developers.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]