kconfig: remove CONFIG_KERNEL_CI infrastructure

Remove the CONFIG_KERNEL_CI Kconfig infrastructure now that all
workflows have been converted to use their own internal loop
configurations or SOAK_DURATION:

- Remove Kconfig.kernel-ci file with all kernel-ci options
- Remove kernel-ci menu and source from Kconfig.kdevops
- Remove CONFIG_KERNEL_CI from kernel-testing defconfig
- Update fstests documentation to mention SOAK_DURATION instead

This completes the removal of the confusing CONFIG_KERNEL_CI feature
that was originally added for loop testing but has been superseded
by better architectural choices.

Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <[email protected]>

Author: mcgrof

defconfigs/kernel-testing

@@ -2,5 +2,4 @@ CONFIG_KDEVOPS_TRY_REFRESH_REPOS=y
 CONFIG_KDEVOPS_TRY_UPDATE_SYSTEMS=y
 CONFIG_KDEVOPS_TRY_INSTALL_KDEV_TOOLS=y
 CONFIG_GIT_ALTERNATIVES=y
-CONFIG_KERNEL_CI=y
 CONFIG_WORKFLOW_KOTD_ENABLE=y

docs/fstests.md

@@ -137,15 +137,10 @@ of a baseline by running fstests in a loop 100 times.  If no new failures have
 been found we consider that we have a high confidence in a baseline and then
 it can be used to verify if new development changes are not causing a regression.
 
-The amount of loops you choose to test with fstests is configurable
-with `CONFIG_KERNEL_CI_STEADY_STATE_GOAL`. We default to 100. This value
-is chosen for a few reasons:
-
-  * Running fstests 100 times takes about 1 week
-  * This is a sensible litmus test to ensure no regressions are
-    introduced with a new delta of patches, if you want to build confidence
-    in some possibly intrusive changes to Linux, or backport some patches
-    without regressing the kernel.
+The preferred method for long-term testing with fstests is to use the
+SOAK_DURATION feature, which allows specific tests designed for soak
+testing to run for extended periods. This provides a more targeted approach
+to stress testing compared to simply running all tests in a loop.
 
 The value originally comes from kdevops use at SUSE Linux enterprise
 distributions, as a litmus test to validate kernel releases, so to ensure

kconfigs/Kconfig.kdevops

@@ -193,9 +193,6 @@ menu "Ansible post-bring up provisioning configuration"
 source "kconfigs/Kconfig.ansible_provisioning"
 endmenu
 
-menu "Kernel continous integration configuration"
-source "kconfigs/Kconfig.kernel-ci"
-endmenu
 
 menu "Ansible Configuration"
 source "kconfigs/Kconfig.ansible_cfg"