]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core.git/commit
oe-build-perf-report: relax metadata matching rules
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 16 Nov 2025 23:44:30 +0000 (23:44 +0000)
committerSteve Sakoman <steve@sakoman.com>
Wed, 19 Nov 2025 16:28:19 +0000 (08:28 -0800)
commitff72b41a3f0bf1820405b8782f0d125cd10e3406
tree0d4ab7fb1fd74de18f171dd9c9fe9c949788011a
parente1c1b4b5100e08b63a2e6e5ff608f79e7b202649
oe-build-perf-report: relax metadata matching rules

As the poky repository is no longer used, measurements are indexed using
the oe-core commit. But as bitbake, oe-core and meta-yocto are now
retrieved from separate gits, while measuring performances for a given branch
at some time interval, we can get the same commit for oe-core but
different ones for bitbake or meta-yocto. As a consequence, metadata
associated with the same index (oe-core commit) might differ.

To work around this, relax the equality checks for commit, commit_time
and commit_count since they might no longer match.

Ideally we'd group them into separate results but for now, treat them
as being the same.

[Based on work from Mathieu Dubois-Briand but fixed differently]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit e7dc42e30c76bf0fbb4d3cc019bbec675bac55fa)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
scripts/lib/build_perf/report.py