Commit f1a27850 authored by Steven Rostedt's avatar Steven Rostedt Committed by Steven Rostedt

ktest: Copy the last good and bad configs in config_bisect

During the config_bisect, in case of failure, it is nice to have
the last good and bad .configs that were used. This would let
us restart the config_bisect from those configs.

Copy the last good config into the output dir as config_good,
and the last bad config as config_bad.
Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
parent eec56460
...@@ -1281,6 +1281,8 @@ sub process_passed { ...@@ -1281,6 +1281,8 @@ sub process_passed {
delete $config_list{$config}; delete $config_list{$config};
} }
} }
doprint "config copied to $outputdir/config_good\n";
run_command "cp -f $output_config $outputdir/config_good";
} }
sub process_failed { sub process_failed {
...@@ -1358,6 +1360,8 @@ sub run_config_bisect { ...@@ -1358,6 +1360,8 @@ sub run_config_bisect {
doprint "This config had a failure.\n"; doprint "This config had a failure.\n";
doprint "Removing these configs that were not set in this config:\n"; doprint "Removing these configs that were not set in this config:\n";
doprint "config copied to $outputdir/config_bad\n";
run_command "cp -f $output_config $outputdir/config_bad";
# A config exists in this group that was bad. # A config exists in this group that was bad.
foreach my $config (keys %config_list) { foreach my $config (keys %config_list) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment