From: Martin Jansa <martin.jansa@gmail.com>
To: "Proca, Andreea B" <andreea.b.proca@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: error-report-web django-nvd3 version
Date: Thu, 6 Mar 2014 14:46:07 +0100 [thread overview]
Message-ID: <20140306134607.GG26981@jama> (raw)
In-Reply-To: <C76456D50C459F418509335BC413076F169032A3@IRSMSX106.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
On Thu, Mar 06, 2014 at 11:44:54AM +0000, Proca, Andreea B wrote:
> 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 :).
> -----Original Message-----
> From: Martin Jansa [mailto:martin.jansa@gmail.com]
> Sent: Thursday, March 06, 2014 3:32 AM
> To: Proca, Andreea B
> Cc: openembedded-core@lists.openembedded.org
> 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.
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-06 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 1:31 error-report-web django-nvd3 version Martin Jansa
2014-03-06 10:27 ` Paul Eggleton
2014-03-06 11:44 ` Proca, Andreea B
2014-03-06 13:46 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140306134607.GG26981@jama \
--to=martin.jansa@gmail.com \
--cc=andreea.b.proca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox