From: Anton Mikanovich <amikan@ilbers.de>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/5] Use buildstats from OE to generate build charts
Date: Wed, 1 Dec 2021 16:24:49 +0300 [thread overview]
Message-ID: <f1535762-b66f-c73a-48f0-e4dbd723c060@ilbers.de> (raw)
In-Reply-To: <20211119092459.27376-1-ubely@ilbers.de>
19.11.2021 12:24, Uladzimir Bely wrote:
> Changes since v2:
> - Use more straightforward USE_BUILDSTATS = "1" in local.conf to enable
> the buildstats feature, don't use OE-specific USER_CLASSES.
> - Avoid forking buildstats.bbclass, use it from OE `as is`.
> Changes since v1:
> - rebased on latest `next` rechecked in CI.
>
> 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.
>
> Note: After creating rootfs, buildstats.bbclass checks its size by
> executing "du -sh" on the directory. While in Isar rootfs is created
> under root, some "-x" directories (/var/cache/apt/archives/partial
> or /root) may be unavailable for this check. So, the calculated size
> may differ from the real one.
>
> The first patch in the series is borrowed from 'sstate' series.
> So, if 'sstate' patchset is applied before this one, the patch
> should be skipped.
>
> Adriaan Schmidt (1):
> oe imports in central location
>
> Uladzimir Bely (4):
> buildstats: Borrow buildstats and pybootchartgui from OE
> buildstats: Fixes to work with bbclass in ISAR
> buildstats: Enable buildstats in default configuration
> doc: Add buildstats section in user manual
>
> doc/user_manual.md | 22 +
> meta-isar/conf/local.conf.sample | 3 +
> meta/classes/base.bbclass | 28 +
> meta/classes/buildstats.bbclass | 295 ++++++
> meta/classes/dpkg-base.bbclass | 5 -
> meta/classes/patch.bbclass | 5 -
> meta/conf/bitbake.conf | 4 +
> 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 ++
> 25 files changed, 4172 insertions(+), 10 deletions(-)
> 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
>
Applied to next, thanks.
--
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
prev parent reply other threads:[~2021-12-01 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 9:24 Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 1/5] oe imports in central location Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 2/5] buildstats: Borrow buildstats and pybootchartgui from OE Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 3/5] buildstats: Fixes to work with bbclass in ISAR Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 4/5] buildstats: Enable buildstats in default configuration Uladzimir Bely
2021-11-19 9:24 ` [PATCH v3 5/5] doc: Add buildstats section in user manual Uladzimir Bely
2021-12-01 13:24 ` Anton Mikanovich [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=f1535762-b66f-c73a-48f0-e4dbd723c060@ilbers.de \
--to=amikan@ilbers.de \
--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