Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #111
Closed
Open
Issue created Nov 27, 2014 by Derek Bruening@derekbrueningContributor

support running tests in parallel

From [email protected] on April 08, 2009 11:07:09

The latest CTest (will become 2.6.4) support running tests in parallel. As part of getting the Windows runall tests working we should tweak them to support parallel execution, which they do not today due to two factors:

  • they all run the same apps (calc.exe, notepad.exe) and thus can trip over each other's registry settings
  • they use closewnd.c which closes an app with a certain name in its
    title, which will close all instances of the app

My proposed solution is:

  • make a copy of calc.exe or notepad.exe and name it with the test name
  • have closewnd.c find the window and do a clean shutdown (as opposed to drkill) using the pid instead of the name. this can be done by using EnumWindows() to enumerate top-level windows and then using GetWindowThreadProcessId() to find the one owned by the target pid.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=111

Assignee
Assign to
Time tracking