Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • 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
  • #3934
Closed
Open
Issue created Nov 26, 2018 by James Willenbring@jmwilleOwner

Framework: CDash interprets failed shared library load as a "not run" rather than as a fail

Created by: csiefer2

@trilinos/framework @trilinos/muelu

As I discovered from our testing, if a program cannot find a shared library at run time (and the test fails to run), cdash reports that as a "Not Run" which has no useful screen output. This case really ought to be a run failure, so we can see the effect of the failed library load.

See: https://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=4215058

Assignee
Assign to
Time tracking