Skip to content

Commit

Permalink
ktest: Copy the last good and bad configs in config_bisect
Browse files Browse the repository at this point in the history
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: Steven Rostedt <rostedt@goodmis.org>
  • Loading branch information
Steven Rostedt authored and Steven Rostedt committed Nov 18, 2010
1 parent eec5646 commit f1a2785
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions tools/testing/ktest/ktest.pl
Original file line number Diff line number Diff line change
Expand Up @@ -1281,6 +1281,8 @@ sub process_passed {
delete $config_list{$config};
}
}
doprint "config copied to $outputdir/config_good\n";
run_command "cp -f $output_config $outputdir/config_good";
}

sub process_failed {
Expand Down Expand Up @@ -1358,6 +1360,8 @@ sub run_config_bisect {

doprint "This config had a failure.\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.
foreach my $config (keys %config_list) {
Expand Down

0 comments on commit f1a2785

Please sign in to comment.