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
  • #5360
Closed
Open
Issue created Feb 16, 2022 by Derek Bruening@derekbrueningContributor

Run all tests in release build in long suite on master merge

Historically we've been focused on debug-build tests, under the assmption that it is pretty rare for an issue to happen only in release build. Debug build has extra checks that catch more errors. Today we run only a subset of tests in release build, based on that assumption and to keep the PR CI time down. But: we have a separate "long" suite on master merge where the time doesn't matter as much. We should enable all the tests in release-build there.

This is becoming more important as we have lately been seeing release-build-only failures: #4928 (closed), #4954 (closed), #2417 drcachesim.coherence.

Assignee
Assign to
Time tracking