All of
 help / color / mirror / Atom feed
From: Guillaume Tucker <>
To: Hans Verkuil <>
Subject: Re: media/master v4l2-compliance on vivid: 236 tests, 0 regressions (media_v5.1-2-16-gfc8670d1f72b)
Date: Fri, 24 May 2019 09:38:39 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Hans,

On 16/05/2019 07:41, Hans Verkuil wrote:
> Hi Guillaume,
> I have a few questions/suggestions:

Thanks for the feedback!  It's good to start seeing these reports
on the linux-media mailing list.  And sorry for the slow reply, I
was away.

> On 5/15/19 9:04 PM, bot wrote:
>> media/master v4l2-compliance on vivid: 236 tests, 0 regressions (media_v5.1-2-16-gfc8670d1f72b)
>> Test results summary
>> --------------------
>> V4L2 Compliance on the vivid driver.
>> This test ran "v4l2-compliance -s" from v4l-utils:
> I'd just link directly to the git repo instead of the wiki:

Sure, I thought this had been agreed before but it's easy to

> You should add the v4l-utils commit that's used to compile v4l2-compliance.
> That's important information to have. I assume that this test always uses the
> latest version of v4l-utils?

This information is in the detailed results, but the detailed
results are only shown when there are some failures.  So we'll
rework that a bit.

For example, from the v4l2-compliance-uvc report:

Test failures
1  | rk3399-gru-kevin       | arm64 |  52 total:  43 PASS   9 FAIL   0 SKIP

  Config:      defconfig
  Compiler:    gcc-8 (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0)
  Lab Name:    lab-collabora
  Plain log:
  HTML log:
  Test Git:    git://
  Test Commit: 0d61ddede7d340ffa1c75a2882e30c455ef3d8b8

The git repo and commit hash here show you which version of
vl4-utils was used.

At the moment, the v4l2-compliance is part of a rootfs which gets
updated each time production code gets updated,
which is typically once a week.  This can be improved to have the
rootfs updates independent from the rest, then we could trigger
rebuilds every time v4l-utils changes, but there are a few things
to take into consideration before we can do this safely.

>> See each detailed section in the report below to find out the git URL and
>> particular revision that was used to build the test binaries.
>>   Tree:    media
>>   Branch:  master
>>   Kernel:  media_v5.1-2-16-gfc8670d1f72b
> I assume this is the version of the host kernel, right? Perhaps calling this
> "Host Kernel:" would be less ambiguous.

I have to say I fail to see any ambiguity here: KernelCI is about
testing kernels, and this tells you the kernel revision under
test.  Calling it "host" kernel might actually be confusing when
running with QEMU as people may think it's the version on the
host server running the test.

>>   URL:
>>   Commit:  fc8670d1f72b746ff3a5fe441f1fca4c4dba0e6f
>> 1  | qemu                   | arm64 | 118 total: 118 PASS   0 FAIL   0 SKIP
>> 2  | qemu                   | arm   | 118 total: 118 PASS   0 FAIL   0 SKIP  
> Even if everything was OK, I think it would still be useful to have a link
> to the full test report.

Yes, that is essentially the same issue as with the v4l-utils
version as I described above.  The detailed results show a link
to the console output, which isn't just a clean v4l2-compliance
log but it's better than nothing.

We may also add a feature to publish some files alongside the
parsed test results, and in the case of v4l2-compliance it would
typically be the plain output of the test suite that developers
are familiar with.  It's not a supported feature right now as
only the raw console log is sent from the device to the database.

Best wishes,

  reply	other threads:[~2019-05-24  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 19:04 bot
2019-05-16  6:41 ` Hans Verkuil
2019-05-24  8:38   ` Guillaume Tucker [this message]
2019-05-24  8:44     ` Hans Verkuil
2019-05-24  9:05       ` Guillaume Tucker
2019-05-24  9:20         ` Hans Verkuil
2019-05-24  9:27           ` Guillaume Tucker

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: media/master v4l2-compliance on vivid: 236 tests, 0 regressions (media_v5.1-2-16-gfc8670d1f72b)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.