Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-common
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 24
    • Merge Requests 24
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-common
  • Issues
  • #38

Closed
Open
Opened Jul 26, 2016 by Ansgar Burchardt@ansgar
  • Report abuse
  • New issue
Report abuse New issue

Increase default `DUNE_MAX_TEST_CORES` to 4?

I'm wondering whether it would be good to increase DUNE_MAX_TEST_CORES from 2 to 4. There are some interesting things that can happen on grids with more than two processes: in particular not every other process must be a direct neighbor, vertices can be part of more processes (e.g. the center in a 2x2 grid). These cases should also be covered by the tests enabled by default, but cannot when parallel tests are only run with 2 ranks.

As an example dune-grid's test-parallel-ug seems to pass with 1 and 2 processes, but currently fails with more (but it isn't run in parallel by default yet).

Assignee
Assign to
DUNE 3.0.0
Milestone
DUNE 3.0.0
Assign milestone
Time tracking
None
Due date
None
1
Labels
discussion
Assign labels
  • View project labels
Reference: core/dune-common#38