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
  • #3479
Closed
Open
Issue created Mar 26, 2019 by Derek Bruening@derekbrueningContributor

Run at least a few release-build tests on Travis

In light of a serious regression crashing all drcachesim/drmemtrace uses in #3478 (closed) which was not detected pre-commit but in our post-commit CDash tests, this issue proposes adding at least some subset of tests to be run in release build on Travis. The reason we don't run all of them is to keep the pre-commit time down to something reasonable.

I'm proposing giving a few key tests "TRAVIS" labels and run with "-L TRAVIS". We're already doing the release build on Travis so a few tests won't add too much time.

For reference on how long it takes to build vs run tests, here are the numbers on my CDash Linux machine:

debug-internal-64 build: 1:54 tests: 10:28

release-external-64 build: 1:42 tests: 6:13

Assignee
Assign to
Time tracking