linux/poky.git/meta/classes/buildstats.bbclass, branch yocto-4.0.7

buildstats.bbclass: log host data on failure to task specific file

2021-07-10T21:42:22+00:00

host data, for both interval and failure, was previously logged into the same file which was difficult to read as the files file were usually large. host data is now logged into separate files, for each type of logging (failure and interval) and also for each failed task making it easier to read/parse. (From OE-Core rev: 1a0fb3c0794f4e66086e567a297b4d9379c6b8f3) Signed-off-by: Sakib Sajal Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

buildstats.bbclass: collect data in the same file.

2021-04-27T22:43:57+00:00

Previously "at interval" and "on failure" logs were collected in separate files. Collect both types of logging in the same file for better analysis. Introduced new variable which allows different set of commands to be run by the different logging, interval or failure. The variables are BB_LOG_HOST_STAT_CMDS_INTERVAL and BB_LOG_HOST_STAT_CMDS_FAILURE respecteviely. (From OE-Core rev: 4fbf422351668f755a14811ac39161c889087e81) Signed-off-by: Sakib Sajal Signed-off-by: Richard Purdie

buildstats.bbclass: improve timeout handling

2021-03-11T14:00:36+00:00

The subprocess that runs the commands periodically times out prematurely even when there is sufficient time available within the given interval for the commands to run. This change improves timeout handling and give all the commands equal time to run. (From OE-Core rev: 74e5c438025ed42cfacb993261dc664c3b7959a8) Signed-off-by: Sakib Sajal Signed-off-by: Richard Purdie

buildstats.bbclass: add functionality to collect build system stats

2021-01-17T11:28:13+00:00

There are a number of timeout and hang defects where it would be useful to collect statistics about what is running on a build host when that condition occurs. This adds functionality to collect build system stats on a regular interval and/or on task failure. Both features are disabled by default. To enable logging on a regular interval, set: BB_HEARTBEAT_EVENT = "" BB_LOG_HOST_STAT_ON_INTERVAL = Logs are stored in ${BUILDSTATS_BASE}//host_stats To enable logging on a task failure, set: BB_LOG_HOST_STAT_ON_FAILURE = "" Logs are stored in ${BUILDSTATS_BASE}//build_stats The list of commands, along with the desired options, need to be specified in the BB_LOG_HOST_STAT_CMDS variable delimited by ; as such: BB_LOG_HOST_STAT_CMDS = "command1 ; command2 ;... ;" (From OE-Core rev: edb7098e9e0a8978568a45057c1c3ad2c6cacd67) Signed-off-by: Sakib Sajal Signed-off-by: Richard Purdie

buildstats.bbclass: Do not recalculate build start time

2020-06-04T12:27:32+00:00

The build start time is recorded in __timedata_build, which we should use rather than recalculating it. (From OE-Core rev: b723e9a4de67f33f61f2e7fe36ea451a46840b3e) Signed-off-by: Junling Zheng Signed-off-by: Richard Purdie

buildstats.bbclass: Remove useless variables

2020-06-04T12:27:32+00:00

Remove useless variables bn and bsdir in write_task_data(). (From OE-Core rev: de26d6ce9d2154b5bb51491d9f4bd590cb5a0fc7) Signed-off-by: Junling Zheng Signed-off-by: Richard Purdie

buildstats: Replace 'is' with '==' in python condition check expression

2019-12-15T09:10:46+00:00

python 3.8 has started to throw this as a warning but usage is wrong see [1], it seems to be working by accident and not design. Fixes SyntaxWarning: "is" with a literal. Did you mean "=="? [1]: https://bugs.python.org/issue34850 (From OE-Core rev: c3cb6bc21f3f84e2ed103b6438516ab85222faa9) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

buildstats.bbclass: Avoid index exception in /proc/PID/io parsing

2017-03-01T23:27:10+00:00

There is some probability (depends on system load) to get empty or line containing "0" as the last line while reading /proc/PID/io. Avoid build failure by checking if line contains separator ":" before split. (From OE-Core rev: b26feaf51af55f17fad79dbd53dd3ec0a37c38ff) Signed-off-by: Pavel Modilaynen Signed-off-by: Daniel Lublin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/buildstats: don't expand variable pointing to SystemStats

2017-01-09T13:39:11+00:00

We're placing an object into the datastore - it's very definitely not something we want to be expanding. (From OE-Core rev: adfee41d2b1edbd2abd09f9101c359919e21e5d6) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie