From: Kees Cook <keescook@chromium.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>,
"automated-testing@yoctoproject.org"
<automated-testing@yoctoproject.org>,
kernelci@groups.io,
clang-built-linux <clang-built-linux@googlegroups.com>,
Vishal Bhoj <vishal.bhoj@linaro.org>,
Antonio Terceiro <antonio.terceiro@linaro.org>,
Remi Duraffort <remi.duraffort@linaro.org>
Subject: Re: #KCIDB engagement report
Date: Tue, 1 Jun 2021 13:26:35 -0700 [thread overview]
Message-ID: <202106011315.432A65D6@keescook> (raw)
In-Reply-To: <CAKwvOdmwRV6R6dcpcSL06SNVQ1_JwvOJMZPYiHKvjSx4sf_95g@mail.gmail.com>
On Mon, May 24, 2021 at 10:38:22AM -0700, 'Nick Desaulniers' via Clang Built Linux wrote:
> On Mon, May 24, 2021 at 12:50 AM Nikolai Kondrashov
> <Nikolai.Kondrashov@redhat.com> wrote:
> > [...]
> > KernelCI native
> > Sending (a lot of) production build and test results.
> > https://staging.kernelci.org:3000/?var-origin=kernelci
> > [...]
Apologies for the thread hijack, but does anyone know what's happening
with kselftest? It seems missing from the listed[1] build artifacts, but
it is actually present[2] (and I see the logs for generating the tarball
there too), but I can't find any builds that actually run the tests?
(Or how do I see a top-level list of all tests and search it?)
Thanks!
-Kees
[1] https://kcidb.kernelci.org/d/build/build?orgId=1&var-dataset=kernelci04&var-id=kernelci:kernelci.org:60b654321456eb7654b3afa6&fullscreen&panelId=17
[2] https://storage.kernelci.org//mainline/master/v5.13-rc4-11-gc2131f7e73c9/x86_64/x86_64_defconfig+x86-chromebook+kselftest/gcc-8/
--
Kees Cook
next prev parent reply other threads:[~2021-06-01 20:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 7:50 #KCIDB engagement report Nikolai Kondrashov
2021-05-24 17:38 ` Nick Desaulniers
2021-05-25 10:32 ` Nikolai Kondrashov
2021-06-01 19:10 ` Nick Desaulniers
2021-06-07 11:13 ` Nikolai Kondrashov
2021-06-07 18:09 ` Nick Desaulniers
2021-06-10 9:15 ` Nikolai Kondrashov
2021-06-10 23:38 ` Nick Desaulniers
2021-06-11 10:50 ` Nikolai Kondrashov
2021-06-11 11:10 ` Nikolai Kondrashov
2021-06-01 20:26 ` Kees Cook [this message]
2021-06-11 16:11 ` Guillaume Tucker
2021-06-15 9:58 ` Nikolai Kondrashov
2021-06-15 10:36 ` Guillaume Tucker
2021-06-15 22:03 ` Kees Cook
2021-06-15 22:23 ` Guillaume Tucker
2021-06-15 23:02 ` Kees Cook
2021-06-30 8:54 ` Guillaume Tucker
2021-06-30 18:19 ` Kees Cook
[not found] <8543af6d-28cf-6117-4dad-76aafea4b6f7@redhat.com>
2022-11-18 10:06 ` Guillaume Tucker
-- strict thread matches above, loose matches on Subject: below --
2022-07-23 11:50 Nikolai Kondrashov
2022-06-20 12:48 Nikolai Kondrashov
2022-04-22 14:06 Nikolai Kondrashov
2022-01-27 14:41 Nikolai Kondrashov
2021-10-21 12:33 Nikolai Kondrashov
2021-08-23 12:37 Nikolai Kondrashov
2021-08-25 17:39 ` Nick Desaulniers
2021-06-16 13:54 Nikolai Kondrashov
2021-04-15 8:54 Nikolai Kondrashov
2021-03-18 10:34 Nikolai Kondrashov
2021-02-18 10:47 Nikolai Kondrashov
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=202106011315.432A65D6@keescook \
--to=keescook@chromium.org \
--cc=Nikolai.Kondrashov@redhat.com \
--cc=antonio.terceiro@linaro.org \
--cc=automated-testing@yoctoproject.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kernelci@groups.io \
--cc=ndesaulniers@google.com \
--cc=remi.duraffort@linaro.org \
--cc=vishal.bhoj@linaro.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.