linux/poky.git/bitbake/lib/bb/monitordisk.py, branch uninative-2.1

bitbake: monitordisk: add event

2016-12-07T10:42:22+00:00

The current disk usage is interesting and may be worth logging over time as part of the build statistics. Instead of re-implementing the code and the configuration option (BB_DISKMON_DIRS), the information gathered by monitordisk.py is made available to buildstats.bbclass via a new event. This has pros and cons: - there is already a useful default configuration for "interesting" directories - no code duplication - on the other hand, users cannot configure recording separately from monitoring (probably not that important) (Bitbake rev: f065ac17d0031dca6309ddbff18c8792630de865) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

bitbake: monitordisk.py: minor code and comment cleanup

2016-12-07T10:42:22+00:00

There's no need to encode and decode the hash key as a single string, a tuple works just fine. Iterating over entries can be written more concisely. Entries in the stat results are integers, not floating point values. (Bitbake rev: 3c943e989964382c0b819d92de26a0c914ebed33) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

bitbake: bitbake: remove True option to getVar calls

2016-11-30T15:48:09+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$ (Bitbake rev: 3b45c479de8640f92dd1d9f147b02e1eecfaadc8) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

bitbake: bitbake: Update logger.warn() -> logger.warning()

2016-05-11T09:34:30+00:00

python deprecated logger.warn() in favour of logger.warning(). This is only used in bitbake code so we may as well just translate everything to avoid warnings under python 3. Its safe for python 2.7. (Bitbake rev: 676a5f592e8507e81b8f748d58acfea7572f8796) Signed-off-by: Richard Purdie

bitbake: monitordisk: don't log when not monitoring a filesystem for inodes

2014-09-29T11:08:48+00:00

Writing a log that the filesystem isn't being monitored for inode usage just confuses users who are not aware about the nature of inodes in their filesystem, so don't say anything, just silently disable the monitor. In general this only happens on filesystems which don't have a limit on inodes. (Bitbake rev: ca93bc84ee5fb94a50c11c47e4d212d7da649e24) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: lib/bb/*.py: Typo fixes/grammar/comment fixes, nothing functional.

2014-08-25T07:57:45+00:00

(Bitbake rev: 587b144ee409d444494d8d7f2d1c53ede8f7c953) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

bitbake: monitordisk: lower inode check warning to note

2013-10-18T15:02:16+00:00

Filesystems like btrfs and reiserfs sets the inode count to 0, since they don't have an inode concept. This is expected, and having a warning show up every time you run bitbake can cause undue concern. (Bitbake rev: f3ac2d3678f48c68a250a0a20c08cf8687322d38) Signed-off-by: Olof Johansson Signed-off-by: Richard Purdie

bitbake: lib/bb/monitordisk.py: fix spelling in error text

2013-10-02T14:41:21+00:00

(Bitbake rev: 78efda1224a99ed3d2ca6befb9fd719d82f6b0ae) Signed-off-by: Erik Botö Signed-off-by: Richard Purdie

bitbake: monitordisk.py: disable inode checking for btrfs

2013-04-15T14:57:31+00:00

The btrfs doesn't have static inode, so disable the inode check for it, the previouse patch has set it: minInode = None But this is incorrect, the minInode is just a temporary variable, it should be: self.devDict[k][2] = None [YOCTO #3609] (Bitbake rev: 7e45149c292bc92314af9b42962fde8f603a179f) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: monitordisk.py: monitor disks based on path

2013-03-19T13:55:38+00:00

The previous monitor is based on the disk, and one disk only can have one action, this limits its function, for example we set this in the current local.conf: BB_DISKMON_DIRS = "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100GM,1K" Before: * If TMPDIR, DL_DIR and SSTATE_DIR are on the same disk partition, only the last line "ABORT,${SSTATE_DIR},100GM,1K" works * If TMPDIR, DL_DIR and SSTATE_DIR are on the different disk partitions, only the last three lines (ABORT) work. These are not what we expect, now: * We monitor the disk based on the path and action, so all the six lines will work no matter whether they are on the same disk partition or not. * The out put format will be: WARNING: The free space of /path/to/directory (device) is running low (XXGB left) [YOCTO #3995] (Bitbake rev: e22a576672ee4a40b44f7a826a78a77fc07e9177) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie