From: Laura Abbott <labbott@redhat.com>
To: Pintu Kumar <pintu.ping@gmail.com>,
kernel test robot <xiaolong.ye@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
shuah@kernel.org, dvhart@infradead.org,
Bamvor Zhang Jian <bamvor.zhangjian@linaro.org>,
Pintu Kumar <pintu_agarwal@yahoo.com>,
lkp@01.org
Subject: Re: [lkp-robot] [android/ion] 5fb70554d6: kernel_selftests.android.make_fail
Date: Mon, 30 Oct 2017 14:02:56 -0700 [thread overview]
Message-ID: <8e7d8bbb-ec51-b693-aa35-1af73c163299@redhat.com> (raw)
In-Reply-To: <CAOuPNLi+yfbO00o-TKRpaDKT6ZhOcdho6oY21X9m6drK=xWuzA@mail.gmail.com>
On 10/30/2017 12:12 AM, Pintu Kumar wrote:
> On Sun, Oct 29, 2017 at 7:51 PM, kernel test robot
> <xiaolong.ye@intel.com> wrote:
>>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: 5fb70554d68e2ea032b6a28b082801d8b7b76cb8 ("android/ion: userspace test utility for ion buffer sharing")
>> url: https://github.com/0day-ci/linux/commits/Pintu-Agarwal/android-ion-userspace-test-utility-for-ion-buffer-sharing/20171025-022548
>>
>>
>> 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-5fb70554d68e2ea032b6a28b082801d8b7b76cb8
>> 2017-10-26 22:18:16 ln -sf /usr/bin/gcc-5 /usr/bin/gcc
>>
>> 2017-10-26 22:18:16 make run_tests -C android
>> make: Entering directory '/usr/src/linux-selftests-x86_64-rhel-7.2-5fb70554d68e2ea032b6a28b082801d8b7b76cb8/tools/testing/selftests/android'
>> make[1]: Entering directory '/usr/src/linux-selftests-x86_64-rhel-7.2-5fb70554d68e2ea032b6a28b082801d8b7b76cb8/tools/testing/selftests/android/ion'
>> gcc -I../../../../../drivers/staging/android/uapi/ -Wall -O2 -g ionapp_export.c ipcsocket.c ionutils.c -o ionapp_export
>> In file included from ionapp_export.c:28:0:
>> ionutils.h:4:17: fatal error: ion.h: No such file or directory
>> compilation terminated.
>> In file included from ionutils.c:9:0:
>> ionutils.h:4:17: fatal error: ion.h: No such file or directory
>> compilation terminated.
>
> This utility requires ion.h header file which should be included from
> kernel source tree: drivers/staging/android/ion/uapi/
> This is already mentioned in the ion/Makefile
> Looks like this ion.h is not getting included inside the linux_headers_dir ?
>
> Shall I include the ion.h locally in my selftests?
> Or, is there a better way to include the header directly...
>
>
I can't reproduce this in any of my environments but if I had to guess,
it's because you have
#include "ion.h"
which is supposed to look in the local path.
Thanks,
Laura
next prev parent reply other threads:[~2017-10-30 21:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 18:08 [PATCH 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing Pintu Agarwal
2017-09-26 18:50 ` Pintu Kumar
2017-09-26 19:22 ` Laura Abbott
2017-09-27 14:24 ` Pintu Kumar
2017-09-28 18:11 ` Pintu Kumar
2017-09-28 18:16 ` Pintu Kumar
2017-09-30 4:04 ` Pintu Kumar
2017-10-03 16:48 ` [PATCHv2 " Pintu Agarwal
2017-10-04 0:12 ` Laura Abbott
2017-10-04 11:29 ` Pintu Kumar
2017-10-04 22:07 ` Laura Abbott
2017-10-06 14:28 ` Pintu Kumar
2017-10-09 14:17 ` Pintu Kumar
2017-10-09 21:19 ` Laura Abbott
2017-10-04 7:20 ` Greg KH
2017-10-04 10:54 ` Pintu Kumar
2017-10-14 11:36 ` [PATCHv3 1/1] [tools/selftests]: " Pintu Agarwal
2017-10-17 14:18 ` Shuah Khan
2017-10-17 20:21 ` Laura Abbott
2017-10-17 20:58 ` Shuah Khan
2017-10-18 10:38 ` Pintu Kumar
2017-10-20 14:40 ` Shuah Khan
2017-10-20 15:18 ` Pintu Kumar
2017-10-20 19:21 ` Shuah Khan
2017-10-23 13:41 ` Pintu Kumar
2017-10-23 23:26 ` [PATCHv4 " Pintu Agarwal
2017-10-27 5:34 ` Pintu Kumar
2017-10-27 8:45 ` Greg Kroah-Hartman
2017-10-27 10:00 ` Pintu Kumar
2017-10-29 14:21 ` [lkp-robot] [android/ion] 5fb70554d6: kernel_selftests.android.make_fail kernel test robot
2017-10-30 7:12 ` Pintu Kumar
2017-10-30 21:02 ` Laura Abbott [this message]
2017-10-31 10:21 ` Pintu Kumar
2017-10-31 21:58 ` Laura Abbott
2017-11-01 10:12 ` Pintu Kumar
2017-11-01 10:30 ` Greg Kroah-Hartman
2017-11-01 15:04 ` Shuah Khan
2017-11-01 16:26 ` Pintu Kumar
2017-11-01 16:57 ` Shuah Khan
2017-11-01 17:14 ` Pintu Kumar
2017-11-01 22:38 ` Shuah Khan
2017-11-02 8:53 ` Greg Kroah-Hartman
2017-11-02 14:50 ` Shuah Khan
2017-10-30 22:56 ` [PATCHv4 1/1] [tools/selftests]: android/ion: userspace test utility for ion buffer sharing Laura Abbott
2017-10-31 9:49 ` Pintu Kumar
2017-11-01 17:00 ` [PATCHv5 " Pintu Agarwal
2017-11-02 15:07 ` Shuah Khan
2017-11-02 16:15 ` Pintu Kumar
2017-11-02 16:19 ` Shuah Khan
2017-11-02 17:53 ` Shuah Khan
2017-11-02 23:54 ` Laura Abbott
2017-11-03 0:32 ` Shuah Khan
2017-11-03 4:36 ` Pintu Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e7d8bbb-ec51-b693-aa35-1af73c163299@redhat.com \
--to=labbott@redhat.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@01.org \
--cc=pintu.ping@gmail.com \
--cc=pintu_agarwal@yahoo.com \
--cc=shuah@kernel.org \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®