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
  • #1397

Closed
Open
Created Jun 05, 2017 by James Willenbring@jmwilleMaintainer

Should non-MPI serial builds be part of "clean" build track?

Created by: bartlettroscoe

CC: @trilinos/framework, @maherou

Description:

Should non-MPI "Serial" builds be part of the "Clean" dashboard track?

Currently 2 of the 3 "Clean" builds up on CDash:

  • Linux-GCC-4.7.2-SERIAL_OPT_DEV
  • Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV
  • Linux-gcc-4.9.3-MPI_Release_gcc_4.9.3_openmpi_1.8.7_DEV

are non-MPI SERIAL builds. Why is that? What important Trilinos customer is relying on a non-MPI build of Trilinos?

The only builds that are immediately critical to Trilinos should be in the set of clean builds.

One example of the problem this causes is #1392 (closed).

Assignee
Assign to
Time tracking