From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 0/4] Use buildstats from OE to generate build charts
Date: Mon, 13 Sep 2021 20:23:01 +0200 [thread overview]
Message-ID: <8873b8d9-da7a-ea8b-6565-72f7690e5cf8@siemens.com> (raw)
In-Reply-To: <20210913150355.9973-1-ubely@ilbers.de>
On 13.09.21 17:03, Uladzimir Bely wrote:
> OE uses buildstats to analyze build performance. This patchset ports
> this functionality to Isar.
>
> Build statistics is collected in $BUILDDIR/tmp/buildstats and can be
> converted to PDF file or viewed directly.
>
Do you have some example to share? What can be done with those stats?
Any insights they already provided on the isar build itself?
Jan
> Uladzimir Bely (4):
> buildstats: Borrow buildstats and pybootchartgui from OE
> buildstats: Fix bbclass to work with ISAR
> buildstats: Manage buildstats via USER_CLASSES variable
> doc: Add buildstats section in user manual
>
> doc/user_manual.md | 19 +
> meta-isar/conf/local.conf.sample | 2 +
> meta/classes/buildstats.bbclass | 298 ++++++
> meta/conf/bitbake.conf | 2 +
> meta/lib/buildstats.py | 161 +++
> scripts/pybootchartgui/AUTHORS | 11 +
> scripts/pybootchartgui/COPYING | 340 ++++++
> scripts/pybootchartgui/MAINTAINERS | 3 +
> scripts/pybootchartgui/NEWS | 204 ++++
> scripts/pybootchartgui/README.pybootchart | 37 +
> scripts/pybootchartgui/pybootchartgui.py | 23 +
> .../pybootchartgui/pybootchartgui/__init__.py | 0
> .../pybootchartgui/pybootchartgui/batch.py | 46 +
> scripts/pybootchartgui/pybootchartgui/draw.py | 975 ++++++++++++++++++
> scripts/pybootchartgui/pybootchartgui/gui.py | 348 +++++++
> scripts/pybootchartgui/pybootchartgui/main.py | 1 +
> .../pybootchartgui/pybootchartgui/main.py.in | 183 ++++
> .../pybootchartgui/pybootchartgui/parsing.py | 821 +++++++++++++++
> .../pybootchartgui/process_tree.py | 292 ++++++
> .../pybootchartgui/pybootchartgui/samples.py | 178 ++++
> .../pybootchartgui/tests/parser_test.py | 105 ++
> .../pybootchartgui/tests/process_tree_test.py | 92 ++
> 22 files changed, 4141 insertions(+)
> create mode 100644 meta/classes/buildstats.bbclass
> create mode 100644 meta/lib/buildstats.py
> create mode 100644 scripts/pybootchartgui/AUTHORS
> create mode 100644 scripts/pybootchartgui/COPYING
> create mode 100644 scripts/pybootchartgui/MAINTAINERS
> create mode 100644 scripts/pybootchartgui/NEWS
> create mode 100644 scripts/pybootchartgui/README.pybootchart
> create mode 100755 scripts/pybootchartgui/pybootchartgui.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/__init__.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/batch.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/draw.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/gui.py
> create mode 120000 scripts/pybootchartgui/pybootchartgui/main.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/main.py.in
> create mode 100644 scripts/pybootchartgui/pybootchartgui/parsing.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/process_tree.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/samples.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/tests/parser_test.py
> create mode 100644 scripts/pybootchartgui/pybootchartgui/tests/process_tree_test.py
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-09-13 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 15:03 Uladzimir Bely
2021-09-13 15:03 ` [PATCH 1/4] buildstats: Borrow buildstats and pybootchartgui from OE Uladzimir Bely
2021-09-13 15:03 ` [PATCH 2/4] buildstats: Fix bbclass to work with ISAR Uladzimir Bely
2021-09-13 15:03 ` [PATCH 3/4] buildstats: Manage buildstats via USER_CLASSES variable Uladzimir Bely
2021-09-13 15:03 ` [PATCH 4/4] doc: Add buildstats section in user manual Uladzimir Bely
2021-09-13 18:23 ` Jan Kiszka [this message]
2021-09-14 7:18 ` [PATCH 0/4] Use buildstats from OE to generate build charts Uladzimir Bely
2021-09-14 11:23 ` Jan Kiszka
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=8873b8d9-da7a-ea8b-6565-72f7690e5cf8@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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