Re: bunsen to assist ci/cd testsuite historical analysis needs

[Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>]

Hi Frank,

Thanks for the pointers!

This approach matches well with our CI system.  We already store results in a git repo, and post-process them for publishing to LNT dashboard (e.g., [1]).

Re. ssh access -- could you create an account for linaro-tcwg-bot with ssh key [2]?

[1] http://llvm.validation.linaro.org:38000/db_default/v4/tcwg_gdb_check/graph?plot.14.0=1.14.0&plot.11.2=1.11.2
[2] https://git.linaro.org/ci/dockerfiles.git/tree/tcwg-base/home-data/tcwg-buildslave/.ssh/authorized_keys#n2

Thanks!

--
Maxim Kuvyrkov
https://www.linaro.org

> On Jan 3, 2024, at 02:13, Frank Ch. Eigler <fche@redhat.com> wrote:
> 
> 
> Hi, Maxim -
> 
>> How about a zoom/hangout/etc. call next week?  [Christophe and I are
>> in Europe timezone.]
> 
> I'm so sorry, I didn't see this in time.
> 
>> One obvious opportunity is to make Linaro Toolchain CI submit results
>> to bunsen.  Are there other things we can improve?
> 
> To make this more concrete, your CI system could contribute to the
> sourceware bunsen pool of test results by:
> 
> - creating a temporary git repo in your CI system
> 
> - committing your local testsuite log files, and .bunsen.FOO build
>  metadata files into your git repo using the bunsen t-upload-git-push
>  shell script (or equivalent); see the sourceware buildbot master.cfg
>  for the metadata specifics we use:
>  https://sourceware.org/git/?p=builder.git;a=blob;f=builder/master.cfg;h=d2cb2d0ff1d68196ef1e8a8bcf9c9d7ceeb23211;hb=HEAD#l1267
> 
> - pushing each resulting branch/commit to the sourceware bunsen.git repo
>  (we can get you ssh credentials sufficient for this)
> 
> - deleting your local git repo if you like
> 
> In this scenario, you wouldn't have to run any real bunsen code locally,
> nor publish any data or run a server of your own.  The sourceware
> installation of bunsen would analyze and serve the data shortly after it
> hits git.
> 
> If at some point, you became interested in more, like local long term
> analytics, or compressed log storage, or whatever, we can do something
> more sophisticated.
> 
> - FChE
>