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
  • #3770
Closed
Open
Issue created Aug 07, 2019 by Derek Bruening@derekbrueningContributor

recent drcachesim tests using simple_app fail due to races on the output directory

I'm seeing a set of recently-added drcachesim tests failing when run in parallel:

The following tests FAILED:
	270 - code_api|tool.raw2trace.simple (Failed)
	326 - code_api,satisfy_w_xor_x|tool.drcacheoff.simple (Failed)
Errors while running CTest

They are using simple_app and they collide on the output directory name. We have other tests that do this as well but they're properly marked with dependencies. Unfortunately as we add more we have to mark even more as serial wrt each other. We may want to put a more-maintainable solution in place: a custom name for the output directory or something.

Assignee
Assign to
Time tracking