All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: "Bird, Timothy" <Tim.Bird@sony.com>
Cc: "fuego@lists.linuxfoundation.org"
	<fuego@lists.linuxfoundation.org>,
	"automotive-discussions@lists.linuxfoundation.org"
	<automotive-discussions@lists.linuxfoundation.org>
Subject: Re: [Fuego] Discussion about Fuego unified results format
Date: Thu, 20 Apr 2017 11:13:28 -0700	[thread overview]
Message-ID: <m2k26f2bhz.fsf@baylibre.com> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF1FA6D432@USCULXMSG03.am.sony.com> (Timothy Bird's message of "Thu, 13 Apr 2017 19:19:22 +0000")

"Bird, Timothy" <Tim.Bird@sony.com> writes:

> Based on discussion in our call yesterday, I have a few notes I'd like to make.
> First - for those not involved in the call, here is some introduction.  We are
> working, for the 1.2 release, on unifying the results format produced by Fuego
> tests, to make report generation easier, and support (ultimately) multiple
> report output formats (e.g. HTML, XML, PDF, Excel).  The intent is to support
> all current AGL-JTA reports, previous Fuego reports, and new ones envisioned
> for the system (in the 1.2 release).
>
> Note from the call and about this work are at:
> http://bird.org/fuego/Unified_Results_Format_Project

Has anyone looked at the JSON schema we designed for kernelci.org[1]?  I
wasn't involved in the meetings or call, but from what I can see, one
important thing missing from your current proposal is how to group
related tests together.  In the schema we did for kCI, you can have test
cases grouped into test sets, which in turn can be grouped into a test
suite.  IMO, this is crucial since most tests come as part of a larger
suite.

The kernelci.org project has prototyped this for several testsuites
(kselftest, hackbench, lmbench, LTP, etc.) and were pushing JSON results
using this /test API to our backend for awhile.  But nobody got around
to writing the parsing, reporting stuff yet.

All of that to say the kCI JSON schema has been through through quite a
bit already, and acually used for several test suites, so I think it
would be a good idea to start with that and extend it, so combined
efforts on this JSON test schema could benefit Fuego as well as other
projects.

Kevin

[1] https://api.kernelci.org/schema-test.html
    https://api.kernelci.org/collection-test.html

  parent reply	other threads:[~2017-04-20 18:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 19:19 [Fuego] Discussion about Fuego unified results format Bird, Timothy
2017-04-20  6:40 ` Cai, Song
2017-04-20 18:13 ` Kevin Hilman [this message]
2017-04-21  2:37   ` [cip-dev] " Daniel Sangorrin
2017-04-21  2:37     ` Daniel Sangorrin
2017-04-27  8:02     ` [cip-dev] " Milo Casagrande
2017-04-27  8:02       ` Milo Casagrande
2017-04-28  3:08       ` [cip-dev] " Daniel Sangorrin
2017-04-28  3:08         ` Daniel Sangorrin
2017-04-28  7:31         ` [cip-dev] " Milo Casagrande
2017-04-28  7:31           ` Milo Casagrande
2017-04-26 22:51   ` Bird, Timothy
2017-04-27  8:31     ` Milo Casagrande
2017-04-25  6:34 ` Daniel Sangorrin
2017-04-27  0:37   ` Bird, Timothy

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=m2k26f2bhz.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=Tim.Bird@sony.com \
    --cc=automotive-discussions@lists.linuxfoundation.org \
    --cc=fuego@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.