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
  • #3906
Closed
Open
Issue created Nov 20, 2018 by James Willenbring@jmwilleOwner

Create plan and process for Trilinos testing with new compilers before important Trilinos customers

Created by: bartlettroscoe

@trilinos/framework

Trilinos needs to be testing with newer compiler versions as they come out so that we our customers start testing with newer compilers. That way Trilinos is not always playing catch-up. We need a plan for doing this and we need a process for doing this.

An example of what happens right now is demonstrated in #3497 (closed) and #3499 with the upgrade of ATS-1 ('mutrino', 'trinity') from Intel 17 to Intel 18.

NOTE: I marked this with the label 'epic' since that is what this is.

Assignee
Assign to
Time tracking