Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • James Willenbring
  • Trilinos
  • Issues
  • #1645

Closed
Open
Created Aug 25, 2017 by James Willenbring@jmwilleMaintainer

Dashboard failures, possibly due to incorrectly configured test platform

Created by: mhoemmen

@trilinos/framework @trilinos/tpetra

ascic141, build name Linux-gcc-4.9.3-Sierra_MPI_release_DEV_ETI_SERIAL-ON_OPENMP-OFF_PTHREAD-ON_CUDA-OFF_COMPLEX-ON, has 21 Tpetra test failures. Here is the latest list:

https://testing.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=3072459

They all generate the following output:

p=0: *** Caught standard std::exception of type 'std::runtime_error' :
 
  Constructing View and initializing data with uninitialized execution space
  Traceback functionality not available

I was wondering at first whether the tests were using the default execution space instead of their Node's execution space. However, check out the following failing test output:

https://testing.sandia.gov/cdash/testDetails.php?test=40862107&build=3072459

This is supposed to be for the default Node, yet the test is failing. It looks like this could be a broken configuration.

Assignee
Assign to
Time tracking