public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Carlos Hernandez <ceh@ti.com>
Cc: Dan Rue <dan.rue@linaro.org>,
	kernelci@groups.io, Tim.Bird@sony.com,
	automated-testing@yoctoproject.org, info@kernelci.org
Subject: Re: [Automated-testing] A common place for CI results?
Date: Thu, 16 May 2019 13:05:41 +0100	[thread overview]
Message-ID: <20190516120541.GG5598@sirena.org.uk> (raw)
In-Reply-To: <516df501-82c2-67d5-890e-5a4274c7ce35@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Wed, May 15, 2019 at 06:58:04PM -0400, Carlos Hernandez wrote:
> On 5/15/19 4:33 PM, Dan Rue wrote:

> > This has a few benefits:
> > - Non-opinionated place to hold structured data

Of course structure is opinion :/

> +1
> 
> I like the idea

Me too.

> > The things this leaves me wanting are:
> > - raw data storage. It would be nice if raw data were stored somewhere
> >    permanent in some intermediary place so that later implementations
> >    could happen, and for data that doesn't fit into whatever structure we
> >    end up with.

> If required, we could setup a related table w/ raw data. I believe max cell
> size ~ 100MB per https://cloud.google.com/bigquery/quotas

> However, another approach could be to define the structure version in the
> schema. New fields can be added and left blank for old data.

Versioned structures do make tooling to use the data more difficult to
implement, I think Dan's idea is good especially early on when things
are being tried for the first time.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-05-16 12:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <299272045.11819252.1554465036421.JavaMail.zimbra@redhat.com>
2019-04-05 14:41 ` A common place for CI results? Veronika Kabatova
2019-04-08 22:16   ` Tim.Bird
2019-04-09 13:41     ` Guenter Roeck
2019-04-10  9:28       ` [Automated-testing] " Mark Brown
2019-04-10 17:47       ` Veronika Kabatova
2019-04-10 21:13         ` [Automated-testing] " Kevin Hilman
2019-04-11 16:02           ` Veronika Kabatova
2019-05-14 23:01   ` Tim.Bird
2019-05-15 20:33     ` Dan Rue
2019-05-15 21:06       ` Tom Gall
2019-05-20 15:32         ` Veronika Kabatova
2019-05-28  8:24           ` Guillaume Tucker
2019-05-28 14:45             ` Veronika Kabatova
2019-05-15 22:58       ` [Automated-testing] " Carlos Hernandez
2019-05-16 12:05         ` Mark Brown [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=20190516120541.GG5598@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Tim.Bird@sony.com \
    --cc=automated-testing@yoctoproject.org \
    --cc=ceh@ti.com \
    --cc=dan.rue@linaro.org \
    --cc=info@kernelci.org \
    --cc=kernelci@groups.io \
    /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