Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • tools
  • testing
  • ktest
  • sample.conf
Find file BlameHistoryPermalink
  • Steven Rostedt's avatar
    ktest: Added force stop after success and failure · 1c8a617a
    Steven Rostedt authored Nov 09, 2010
    
    
    Added the options STOP_AFTER_SUCCESS and STOP_AFTER_FAILURE to
    allow the user to give a time (in seconds) to stop the monitor
    after a stack trace or login has been detected. Sometimes the
    kernel constantly prints out to the console and this may cause
    the test to run indefinitely.
    
    Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
    1c8a617a
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7