From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marlon Rodriguez Garcia <marlon.rodriguez-garcia@savoirfairelinux.com>
Cc: bitbake-devel@lists.openembedded.org, toaster@lists.yoctoproject.org
Subject: Re: [toaster][PATCHv3 3/3] toaster: Update eventreplay functionality for new eventlog file structure
Date: Wed, 06 Dec 2023 23:41:56 +0000 [thread overview]
Message-ID: <a086d7dbf22bc3f5106de0276381f006c9411145.camel@linuxfoundation.org> (raw)
In-Reply-To: <1347387869.1559511.1701905526293.JavaMail.zimbra@savoirfairelinux.com>
On Wed, 2023-12-06 at 18:32 -0500, Marlon Rodriguez Garcia wrote:
> I think this could be merge as it is now, and another patch will be
> added to update the Views and the eventreplay lib, can you share the
> patch with the new changes ?
It is sub optimal that the series adds the code to views.py in 1/3 and
then moves it again in 3/3 so I'm leaning to reworking the patches to
clean things up.
The patches still need work since they cause two existing tests to
regress too (as far as I can tell anyway).
The changes to eventreplay merged here:
https://git.yoctoproject.org/poky/commit/?id=3ee5c86da3773deb091e24b98ad592c5d19274fb
Cheers,
Richard
>
> ----- Original Message -----
> From: "richard purdie" <richard.purdie@linuxfoundation.org>
> To: "Marlon Rodriguez Garcia" <marlon.rodriguez-garcia@savoirfairelinux.com>, bitbake-devel@lists.openembedded.org, toaster@lists.yoctoproject.org
> Sent: Wednesday, December 6, 2023 6:02:09 PM
> Subject: Re: [toaster][PATCHv3 3/3] toaster: Update eventreplay functionality for new eventlog file structure
>
> On Wed, 2023-12-06 at 17:43 -0500, Marlon Rodriguez Garcia wrote:
> > Added class EventPlayer to list of libraries under bitbake/bb/ui/
> > Update file read functionality to match new eventlog format
> >
> > Exclude listing of files that don't contain the allvariables definitions used to replay builds
> > This part of the feature should be revisited. Over a long period of time, the BB_DEFAULT_EVENTLOG
> > will exponentially increase the size of the log file and cause bottlenecks when importing.
> >
> > Signed-off-by: Marlon Rodriguez Garcia <marlon.rodriguez-garcia@savoirfairelinux.com>
> > ---
> > lib/bb/ui/eventreplay.py | 85 +++++++++++++++++++++
> > lib/toaster/toastergui/views.py | 131 ++++++++++++--------------------
> > 2 files changed, 132 insertions(+), 84 deletions(-)
> > create mode 100644 lib/bb/ui/eventreplay.py
>
> Our patches overlapped!
>
> I've merged a patch to fix toaster-eventreplay and it is slightly
> different to the code below. The major tweaks are handling a second
> 'allvariables' entry and adding a eventfile.seek(0) to reset the stream
> before calling the player.
>
> We should probably have a standalone patch moving that code from
> toaster-eventreplay to lib/bb/ui/eventreplay.py and making it use it,
> when can then be followed by the patch below to have views.py use it as
> well?
>
> Cheers,
>
> Richard
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#6060): https://lists.yoctoproject.org/g/toaster/message/6060
> Mute This Topic: https://lists.yoctoproject.org/mt/103023929/7896800
> Group Owner: toaster+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/toaster/unsub [marlon.rodriguez-garcia@savoirfairelinux.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2023-12-06 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 22:43 [toaster][PATCHv3 0/3] toaster: feat to import eventlogs] Marlon Rodriguez Garcia
2023-12-06 22:43 ` [toaster][PATCHv3 1/3] toaster: Added feat to import eventlogs files as builds in toaster Marlon Rodriguez Garcia
2023-12-06 22:43 ` [toaster][PATCHv3 2/3] toaster: Update feat to import eventlogs Marlon Rodriguez Garcia
2023-12-06 22:43 ` [toaster][PATCHv3 3/3] toaster: Update eventreplay functionality for new eventlog file structure Marlon Rodriguez Garcia
2023-12-06 23:02 ` Richard Purdie
2023-12-06 23:32 ` Marlon Rodriguez Garcia
2023-12-06 23:41 ` Richard Purdie [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=a086d7dbf22bc3f5106de0276381f006c9411145.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=marlon.rodriguez-garcia@savoirfairelinux.com \
--cc=toaster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).