mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 21:09:03 +02:00
d390ebc18b
With the previous timeout of 5 seconds, there would be builds such as: https://autobuilder.yocto.io/pub/non-release/20210417-13/ which produced 17 files with top output with top running 454 times and that's a bit too much data to analyze for each run. By increasing the timeout, we'll find the worse problems first, fix them and then we can decrease the timeout if needed. (From OE-Core rev: 4f9921db882ed06e0902d34ae06a0eabff4ba86e) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 92b29a09b4c442597d212337b785afb76129ac7c) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
29 lines
708 B
Bash
Executable File
29 lines
708 B
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# oe-time-dd-test records how much time it takes to
|
|
# write <count> number of kilobytes to the filesystem.
|
|
# It also records the number of processes that are in
|
|
# running (R), uninterruptible sleep (D) and interruptible
|
|
# sleep (S) state from the output of "top" command.
|
|
# The purporse of this script is to find which part of
|
|
# the build system puts stress on the filesystem io and
|
|
# log all the processes.
|
|
|
|
usage() {
|
|
echo "Usage: $0 <count>"
|
|
}
|
|
|
|
TIMEOUT=15
|
|
|
|
if [ $# -ne 1 ]; then
|
|
usage
|
|
exit 1
|
|
fi
|
|
|
|
uptime
|
|
timeout ${TIMEOUT} dd if=/dev/zero of=oe-time-dd-test.dat bs=1024 count=$1 conv=fsync
|
|
if [ $? -ne 0 ]; then
|
|
echo "Timeout used: ${TIMEOUT}"
|
|
top -c -b -n1 -w 512
|
|
fi
|