Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-common
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 51
    • Merge Requests 51
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-common
  • Issues
  • #56

Closed
Open
Opened Nov 18, 2016 by Ansgar Burchardt@ansgarOwner

dune_add_test: sets TIMEOUT to 300 by default

The documentation for dune_add_test states that TIMEOUT is an optional parameter overriding the default CMake timeout.

However the implementation just sets the timeout to 300s if no explicit timeout is given, no matter what the CMake default is.

Either the documentation should be updated and state that dune_add_test defaults to a 300s timeout (in which case TIMEOUT could be optional for MPI tests as there already is a default timeout), or the test's TIMEOUT property should only be set if an explicit TIMEOUT was given to dune_add_test.

@dominic: What do you think?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: core/dune-common#56