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
  • #1877
Closed
Open
Issue created Oct 20, 2017 by James Willenbring@jmwilleOwner

Do automated testing for all Trilinos packages that are being released

Created by: bartlettroscoe

CC: @trilinos/framework, @maherou

Description:

It appears that there are packages that are going out with Trilinos releases that are not included in any of the automated builds of Trilinos, including the release branch builds. For example, MOOCHO appears to have been released with Trilinos 12.12 but it does not appear to be tested in any automated builds of Trilinos as shown by, for example:

  • https://testing.sandia.gov/cdash/index.php?project=Trilinos&date=2017-10-19&subproject=MOOCHO

We can't support packages in releases that don't have any automated testing.

Assignee
Assign to
Time tracking