At present the set of config options for kselftest is defined in config/fragments.yaml as just a fixed list of options without reference to what the kernel being tested specifies, resulting in test failures due to missing options. This could be avoided if the kselftest fragment were dynamically generated from the kernel source being tested.
This should probably be built on tuxmake functionality, I have opened kernelci/tuxmake#275 for that.
At present the set of config options for kselftest is defined in config/fragments.yaml as just a fixed list of options without reference to what the kernel being tested specifies, resulting in test failures due to missing options. This could be avoided if the kselftest fragment were dynamically generated from the kernel source being tested.
This should probably be built on tuxmake functionality, I have opened kernelci/tuxmake#275 for that.