1. 13 Jun, 2011 7 commits
    • Steven Rostedt's avatar
      ktest: Have LOG_FILE evaluate options as well · 23715c3c
      Steven Rostedt authored
      The LOG_FILE variable needs to evaluate the $ options as well.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      23715c3c
    • Steven Rostedt's avatar
      ktest: Have wait on stdio honor bug timeout · ecaf8e52
      Steven Rostedt authored
      After a bug is found, the STOP_AFTER_FAILURE timeout is used to
      determine how much output should be printed before breaking out
      of the monitor loop. This is to get things like call traces and
      enough infromation about the bug to help determine what caused it.
      
      The STOP_AFTER_FAILURE is usually much shorter than the TIMEOUT
      that is used to determine when to quit after no more stdio is given.
      
      But since the stdio read uses a wait on I/O, the STOP_AFTER_FAILURE is
      only checked after we get something from I/O. But if the I/O does
      not return any more data, we wait the TIMEOUT period instead, even
      though we already triggered a bug report.
      
      The wait on I/O should honor the STOP_AFTER_FAILURE time if a bug has
      been found.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      ecaf8e52
    • Steven Rostedt's avatar
      ktest: Implement our own force min config · fcb3f16a
      Steven Rostedt authored
      Using the build KCONFIG_ALLCONFIG environment variable to force
      the min config may not always work properly. Since ktest is
      written in perl, it is trivial to read and replace the current
      config with the configs specified by the min config.
      
      Now the min config (and add configs) are read by perl and before
      a make is done, these configs in the .config file are replaced
      by the version in the min config.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      fcb3f16a
    • Steven Rostedt's avatar
      ktest: Add TEST_NAME option · 9064af52
      Steven Rostedt authored
      Searching through several tests, it gets confusing which test result
      is for which test. By adding the TEST_NAME option, the user can tell
      which test result belongs to which test.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      9064af52
    • Steven Rostedt's avatar
      ktest: Add CONFIG_BISECT_GOOD option · 30f75da5
      Steven Rostedt authored
      Currently the config_bisect compares the min config with the
      CONFIG_BISECT config. There may be another config that we know
      is good that we want to ignore configs on. By passing in this
      config it will ignore the options that are set in the good config.
      
      Note: This only ignores the config, it does not (yet) handle
      options that are different between the two configs. If the good
      config has "SLAB" set and the bad config has "SLUB" it will not
      find the bug if the bug had to do with changing these two options.
      
      This is something that I intend to implement in the future.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      30f75da5
    • Steven Rostedt's avatar
      ktest: Add detection of triple faults · f1a5b962
      Steven Rostedt authored
      When a triple fault happens in a test, no call trace nor panic
      is displayed. Instead, the system reboots to the good kernel.
      Since the good kernel may display a boot prompt that matches the
      success string, ktest may think that the test succeeded, when it
      did not.
      
      Detecting triple faults is tricky because it is hard to generalize
      what a reboot looks like. The best that we can come up with for now
      is to examine the Linux banner. If we detect that the Linux banner
      matches the test we want to test, then look to see if we hit another
      Linux banner with a different kernel is booted. This can be assumed
      to be a triple fault.
      
      We can't just check for two Linux banners because things like
      early printk may cause the Linux banner to be displayed twice. Checking
      for different kernel versions should be the safe bet.
      
      If this for some reason detects a false triple boot. A new ktest
      config option is also created:
      
       DETECT_TRIPLE_FAULT
      
      This can be set to 0 to disable this checking.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      f1a5b962
    • Steven Rostedt's avatar
      ktest: Notify reason to break out of monitoring boot · cd4f1d53
      Steven Rostedt authored
      Different timeouts can cause the ktest monitor to break out of the
      loop. It becomes annoying that one does not know the reason why
      it exited the monitor loop. Display the cause of the reason why
      the loop was exited.
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      cd4f1d53
  2. 06 Jun, 2011 5 commits
  3. 04 Jun, 2011 17 commits
  4. 03 Jun, 2011 11 commits