Uploaded image for project: 'Yetus'
  1. Yetus
  2. YETUS-570

Report and optionally kill stale JVMs between unit test modules

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.6.0
    • 0.7.0
    • Precommit
    • None
    • Hide
      <!-- markdown -->

      This change enables two new features:

      * A thread monitor to help determine how `--proclimit` should be configured.

      * A process reaper to automatically eliminate processes that match certain names after some operations to limit the impact of "stuck" unit tests.
      Show
      <!-- markdown --> This change enables two new features: * A thread monitor to help determine how `--proclimit` should be configured. * A process reaper to automatically eliminate processes that match certain names after some operations to limit the impact of "stuck" unit tests.

    Description

      YETUS-561 does a great job of preventing fork bombs and stale processes from destroying machines. However, Yetus should do a better job of:

      a) Reporting when that happens
      b) Preventing that from happening

      Attachments

        1. YETUS-570.03.patch
          24 kB
          Allen Wittenauer
        2. YETUS-570.04.patch
          24 kB
          Allen Wittenauer
        3. YETUS-570.wip.00.patch
          14 kB
          Allen Wittenauer
        4. YETUS-570.wip.01.patch
          14 kB
          Allen Wittenauer
        5. YETUS-570.wip.02.patch
          16 kB
          Allen Wittenauer

        Issue Links

          Activity

            People

              aw Allen Wittenauer
              aw Allen Wittenauer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: