All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexis.lothore@bootlin.com
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: yocto@lists.yoctoproject.org, alexandre.belloni@bootlin.com
Subject: Re: [yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases
Date: Mon, 16 Jan 2023 09:24:45 +0100	[thread overview]
Message-ID: <49a3a253e012e24a2bf9e454d7b56e87@bootlin.com> (raw)
In-Reply-To: <11d00ada72d2ab7ec5476fe09050dc9dfa790606.camel@linuxfoundation.org>

Hi Richard,

On 13/01/2023 19:01, Richard Purdie wrote:
> On Fri, 2023-01-13 at 16:06 +0100, Alexis Lothoré via
> lists.yoctoproject.org wrote:
>> - I also have some uncommitted python unit tests on "previous version
>>   computation", but current scripts directory does not allow proper 
>> unit tests
>> integration. If appropriate, I could submit some minor reworks to make 
>> it viable
>> for testing and submit those tests
> 
> I'm glad you mentioned this! Yes, I think it is important we add some
> tests for this. We can rework these scripts as needed as the project is
> their main user at this point.
Good, I will then add some minor rework to allow introducing unit tests 
alongside
the version computation in the next revision
> 
>> - This new regression checking introduced the need to clone a wider 
>> testresults
>>   history, which is (very) slow on my machine, but I do not now how 
>> slow it is
>> on autobuilder. Could it be an issue for the delivery process ? Does 
>> it need to
>> be smarter on this point ?
> 
> I think it will be slow on the autobuilder and we're going to have to
> do something different to make this work well. My clone still hasn't
> finished and is at 5.75GB of data now (15 mins to get the last 4.5GB)
> and still going.

OK. I observed a quite similar behaviour while pulling manually the 
whole repository,
but I thought it might be linked to network issue on my side. I will add 
a smarter way
based on your suggestion (git ls-remote)

>> - If appropriate, new patch could follow to allow regression reports 
>> generation
>> against multiple revisions : for example we could check for a 
>> milestone build
>> against previous milestone AND previous major release
> 
> I think that is the direction we need to go so yes please!

Noted. If it is OK for you, I will keep this last point for another set 
of patches, once this
initial work is approved and merged.

Regards,

-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2023-01-16  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 15:06 [autobuilder][PATCH 0/2] generate regression reports against proper releases Alexis Lothoré
2023-01-13 15:06 ` [autobuilder][PATCH 1/2] scripts/send-qa-email : clone older history to allow comparing against older releases Alexis Lothoré
2023-01-13 17:46   ` [yocto] " Richard Purdie
     [not found]   ` <1739EF72D910A436.25137@lists.yoctoproject.org>
2023-01-13 23:15     ` Richard Purdie
2023-01-13 15:06 ` [autobuilder][PATCH 2/2] scripts/send-qa-email: Generate regression reports against most relevant release Alexis Lothoré
2023-01-13 18:01 ` [yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases Richard Purdie
2023-01-16  8:24   ` alexis.lothore [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=49a3a253e012e24a2bf9e454d7b56e87@bootlin.com \
    --to=alexis.lothore@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@lists.yoctoproject.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.