public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] charter: Introduce build chart generation tool
Date: Tue, 27 Apr 2021 20:28:28 +0300	[thread overview]
Message-ID: <f36cb66b-e65f-d763-6e48-bee508416571@ilbers.de> (raw)
In-Reply-To: <20210427190111.4c3a1522@md1za8fc.ad001.siemens.net>

27.04.2021 20:01, Henning Schild wrote:
> I think we should not parse those logs and do our own profiling.
> bitbake has profiling support in several flavours. Last time i checked
> isar was missing some library bits that are only in oe.
>
> https://wiki.yoctoproject.org/wiki/Profiling
>
> We should see what is the state of the art in yocto/OE and use that, no
> own inventions. Then see how to get that into isar and possibly massage
> it upstream to get it into isar without forking oe/bitbake bits.
> Or we add "charter" to bitbake and take it from there, in case we fill
> a gap that upstream might have.
>
> Am i correct that this charter is something that oe/bitbake does not
> have?
>
> regards,
> Henning

Yes, this charter is our simple implementation of the same result as 
pybootchart+buildstats can produce in oe.
Buildstats-based solution is also not real-time and integration of the 
whole buildstats into Isar can be tricky.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov


  reply	other threads:[~2021-04-27 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 13:07 Anton Mikanovich
2021-04-22 10:22 ` Anton Mikanovich
2021-04-22 11:17   ` Jan Kiszka
2021-04-27 11:13     ` Anton Mikanovich
2021-04-27 17:01 ` Henning Schild
2021-04-27 17:28   ` Anton Mikanovich [this message]
2021-04-27 18:07     ` Henning Schild

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=f36cb66b-e65f-d763-6e48-bee508416571@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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