All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, guillaume.tucker@gmail.com,
	kernel-build-reports@lists.linaro.org, kernelci@groups.io
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Subject: Re: next/master baseline: 7 runs, 0 regressions (next-20190717)
Date: Wed, 17 Jul 2019 10:43:55 -0500	[thread overview]
Message-ID: <7ha7dcy8ck.fsf@baylibre.com> (raw)
In-Reply-To: <1ab642a0-0157-84c6-a3a8-da3ead6f55b1@collabora.com>

"Guillaume Tucker" <guillaume.tucker@gmail.com> writes:

> On 17/07/2019 12:27, kernelci.org bot wrote:
>> next/master baseline: 7 runs, 0 regressions (next-20190717)
>> 
>> Test results summary
>> --------------------
>> 
>> run | platform                 | arch   | lab                      | compiler | defconfig          | errors
>> ----+--------------------------+--------+--------------------------+----------+--------------------+-------
>>   1 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig | 1/61
>>   2 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig | 1/61
>>   3 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig | 1/61
>>   4 | rk3399-gru-kevin         | arm64  | lab-collabora            | clang-8  | defconfig          | 0/78
>>   5 | rk3399-gru-kevin         | arm64  | lab-collabora            | clang-8  | defconfig          | 0/78
>>   6 | rk3399-gru-kevin         | arm64  | lab-collabora            | gcc-8    | defconfig          | 0/78
>>   7 | rk3399-gru-kevin         | arm64  | lab-collabora            | gcc-8    | defconfig          | 0/78
>
> There's still an issue with this summary table as the "full"
> defconfig is not shown, so there's no way to tell the difference
> between runs 1, 2 or 3.  In the detailed sections, you can see
> that they have CONFIG_ARM_LPAE=y, CONFIG_EFI=y and CONFIG_SMP=n
> on top of the defconfig.
>
> So it could be reformatted this way:
>
>
> run | platform                 | arch   | lab                      | compiler | defconfig                                         | errors
> ----+--------------------------+--------+--------------------------+----------+---------------------------------------------------+-------
>   1 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y | 1/61
>   2 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig+CONFIG_SMP=n                   | 1/61
>   3 | rk3288-veyron-jaq        | arm    | lab-collabora            | gcc-8    | multi_v7_defconfig                                | 1/61
>
>
> which obviously makes the table quite a bit wider.
>
> The width of each column is currently fixed but it could be
> dynamically computed based on the results to avoid superfluous
> spaces:
>
> run | platform          | arch | lab           | compiler | defconfig                                         | errors
> ----+-------------------+------+---------------+----------+---------------------------------------------------+-------
>   1 | rk3288-veyron-jaq | arm  | lab-collabora | gcc-8    | multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y | 1/61
>   2 | rk3288-veyron-jaq | arm  | lab-collabora | gcc-8    | multi_v7_defconfig+CONFIG_SMP=n                   | 1/61
>   3 | rk3288-veyron-jaq | arm  | lab-collabora | gcc-8    | multi_v7_defconfig                                | 1/61
>
>
> Is that still readable enough, or does it get so wide that it's
> becoming too hard to read?

IMO, that's readable, but any more columns, and were going to soon be in
the realm of "not useful to view in email"

Kevin

  reply	other threads:[~2019-07-17 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d2f063d.1c69fb81.64f72.9c8e@mx.google.com>
2019-07-17 13:00 ` next/master baseline: 7 runs, 0 regressions (next-20190717) Guillaume Tucker
2019-07-17 15:43   ` Kevin Hilman [this message]
2019-07-17 17:44     ` Mark Brown

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=7ha7dcy8ck.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=enric.balletbo@collabora.com \
    --cc=guillaume.tucker@gmail.com \
    --cc=kernel-build-reports@lists.linaro.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 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.