On Thu, May 28, 2020 at 11:29 AM Yauheni Kaliuta <yauheni.kaliuta@xxxxxxxxxx> wrote: > > Hi! > > On Thu, May 28, 2020 at 9:16 PM Alexei Starovoitov > <alexei.starovoitov@xxxxxxxxx> wrote: > > > > On Thu, May 28, 2020 at 11:07:09AM -0600, Shuah Khan wrote: > > [...] > > > > > > Here is what CI users are requesting: > > > > > > - ability to install bpf test with other selftests using kselftest > > > install. The common framework is in place and with minor changes > > > to bpf test Makefile, we can make this happen. Others and myself > > > are willing to work on this, so we can get bpf test coverage in > > > test rings. > > > > so you're saying that bpf maintainers and all bpf developers now > > would need to incorporate new 'make install' step to their workflow > > because some unknown CI system that is not even functional decided > > to do 'make install' ? > > That's exactly my point about selfish CI developers who put their > > needs in front of bpf community of developers. > > May be, it can work both ways to make everybody happy :) (I haven't > seen yet fundamental problems why not). then stop pretending and do 'cp -r' for your CI as you were suggested several times already. It works just fine for libbpf CI. Feel free to copy those scripts.
