In _init_kmemleak() we're touching a check_kmemleak file in
${RESULT_BASE} if ${DEBUGFS_MNT/kmemleak} exists as a marker that we
have to check for kmemleak output after running a test.
In 'check' we're calling _init_kmemleak() at around 60% of the file,
but ${RESULT_BASE} is created later at around 62% of the file,
causing the 'touch' in _init_kmemleak() to fail.
Create the ${RESULT_BASE} just after assigning the default value in
get_next_config()
[Eryu: check for mkdir failure and remove the $RESULT_BASE creation
in check.]
Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
- mkdir -p $RESULT_BASE
- if [ ! -d $RESULT_BASE ]; then
- echo "failed to create results directory $RESULT_BASE"
- status=1
- exit
- fi
-
if $OPTIONS_HAVE_SECTIONS; then
echo "SECTION -- $section"
fi
if $OPTIONS_HAVE_SECTIONS; then
echo "SECTION -- $section"
fi
# set default RESULT_BASE
if [ -z "$RESULT_BASE" ]; then
export RESULT_BASE="$here/results/"
# set default RESULT_BASE
if [ -z "$RESULT_BASE" ]; then
export RESULT_BASE="$here/results/"
+ mkdir -p ${RESULT_BASE}
+ if [ ! -d ${RESULT_BASE} ]; then
+ echo "failed to create results directory $RESULT_BASE"
+ exit 1
+ fi
fi
if [ "$FSTYP" == "tmpfs" ]; then
fi
if [ "$FSTYP" == "tmpfs" ]; then