<Tim.Bird@xxxxxxxx> writes: >> -----Original Message----- >> From: linux-kselftest-owner@xxxxxxxxxxxxxxx [mailto:linux-kselftest- >> owner@xxxxxxxxxxxxxxx] On Behalf Of shuah >> Sent: Wednesday, November 27, 2019 5:33 PM >> To: Cristian Marussi <cristian.marussi@xxxxxxx>; Michael Ellerman >> <mpe@xxxxxxxxxxxxxx>; Bird, Tim <Tim.Bird@xxxxxxxx>; linux- >> kselftest@xxxxxxxxxxxxxxx; shuah <shuah@xxxxxxxxxx> >> Subject: Re: kselftest: failed to build with -C tool/testing/selftests when >> KBUILD_OUTPUT is set >> >> On 11/27/19 9:53 AM, Cristian Marussi wrote: ... >> > Well I'm not sure if it covers all the build cases/scenario for CIs and I have >> > only verified that this specific failure seems to work using the toplevel Makefile >> > targets (since the offending commit uses abs-objtree). >> > Anyway $ ./kselftest_install.sh is broken too as of now. >> >> With the revert, it will go back to not having support for relative >> paths :( >> >> I will look into reverting the offending commit or fixing it. > > There may not be many people using relative paths for KBUILD_OUTPUT. > I was affected by it, and it's quite handy given some of the mechanisms in > my CI system, but it's not that hard to work around. (That is, I can just > convert relative paths to absolute paths in a few key places in my > CI, before calling the kernel make.) > > Given that I'm the only person (seemingly) who reported this, and I'm ok > working around it, I think a revert is OK for now. I think that would be best at this stage, every day this is unfixed is another day that selftests aren't getting built and tested. It should just be a matter of passing your output directory to `realpath` somewhere in your script. cheers
