On 08/15/2017 11:55 PM, kernel test robot wrote:
> 
> FYI, we noticed the following commit:
> 
> commit: 83fab1816dadd182539d3928ea5fd53436bcbcb3 ("selftests: futex: convert 
> test to use ksft TAP13 framework")
> url: 
> https://github.com/0day-ci/linux/commits/Shuah-Khan/selftests-futex-convert-test-to-use-ksft-TAP13-framework/20170806-030533
> 
> 
> in testcase: kernel_selftests
> with following parameters:
> 
> 
> test-description: The kernel contains a set of "self tests" under the 
> tools/testing/selftests/ directory. These are intended to be small unit tests 
> to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
> 
> 
> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 
> 64G memory
> 
> caused below changes (please refer to attached dmesg/kmsg for entire 
> log/backtrace):
> 
> 
> 
> 
> KERNEL SELFTESTS: linux_headers_dir is 
> /usr/src/linux-headers-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3
> 2017-08-12 02:23:11 ln -sf /usr/bin/gcc-5 /usr/bin/gcc
> 
> ...
> 
> 2017-08-12 02:31:19 make run_tests -C futex
> make: Entering directory 
> '/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex'
> for DIR in functional; do             \
>       
> BUILD_TARGET=/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/$DIR;
>       \
>       mkdir $BUILD_TARGET  -p;        \
>       make OUTPUT=$BUILD_TARGET -C $DIR all;\
> done
> make[1]: Entering directory 
> '/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional'
> gcc  -g -O2 -Wall -D_GNU_SOURCE -pthread -I../include -I../../   -pthread 
> -lrt  futex_wait_timeout.c ../include/futextest.h ../include/atomic.h 
> ../include/logging.h  -o 
> /usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional/futex_wait_timeout
> In file included from futex_wait_timeout.c:28:0:
> ../include/logging.h: In function 'print_result':
> ../include/logging.h:118:3: warning: implicit declaration of function 
> 'ksft_test_result_error' [-Wimplicit-function-declaration]
>    ksft_test_result_error("%s\n", test_name);
>    ^
> ../include/logging.h: In function 'print_result':
> ../include/logging.h:118:3: warning: implicit declaration of function 
> 'ksft_test_result_error' [-Wimplicit-function-declaration]
>    ksft_test_result_error("%s\n", test_name);

This patch depends on new ksft API that is in linux-kselftest next and also in 
linux-next.
It looks like the failure is because of the missing dependent commit.

c0bb2cf40e42b2fe5c8aa1c4f6f4d09c98839d91
selftests: kselftest framework: add error counter

thanks,
-- Shuah

>    ^
> /tmp/lkp/ccC2uYVW.o: In function `print_result':
> /usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional/../include/logging.h:118:
>  undefined reference to `ksft_test_result_error'
> collect2: error: ld returned 1 exit status
> ../../lib.mk:62: recipe for target 
> '/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional/futex_wait_timeout'
>  failed
> make[1]: *** 
> [/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional/futex_wait_timeout]
>  Error 1
> make[1]: Leaving directory 
> '/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex/functional'
> Makefile:10: recipe for target 'all' failed
> make: *** [all] Error 2
> make: Leaving directory 
> '/usr/src/linux-selftests-x86_64-rhel-7.2-83fab1816dadd182539d3928ea5fd53436bcbcb3/tools/testing/selftests/futex'
> 
> 
> 
> To reproduce:
> 
>         git clone https://github.com/01org/lkp-tests.git
>         cd lkp-tests
>         bin/lkp install job.yaml  # job file is attached in this email
>         bin/lkp run     job.yaml
> 
> 
> 
> Thanks,
> Xiaolong
> 

Reply via email to