common/config: create $RESULT_BASE before dumping kmemleak leaks
authorJohannes Thumshirn <jthumshirn@suse.de>
Fri, 21 Dec 2018 09:16:12 +0000 (10:16 +0100)
committerEryu Guan <guaneryu@gmail.com>
Sat, 22 Dec 2018 12:02:26 +0000 (20:02 +0800)
commit7fc034868d5dce9aaf3517c9c2197221b9a772e4
treec00eccbce66255eda3de9a55e9404ab7f5239428
parent2c97b8691d05aaded0139b1b06667d005123abad
common/config: create $RESULT_BASE before dumping kmemleak leaks

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>
check
common/config