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

Closed
Open
Created Nov 08, 2018 by James Willenbring@jmwilleMaintainer0 of 3 tasks completed0/3 tasks

Framework: Add GCC 7.3 MPI dev->master and PR builds

Created by: jwillenbring

@trilinos/framework

Expectations

We want to have dev->master and PR builds that use GCC 7.3.

Motivation and Context

Due to key customer requirements, GCC 7.2 is an important compiler for Trilinos to build cleanly with. The closest version we currently have on the SEMS NFS mount is 7.3, so we are going to use that, at least for the time being.

Eventually we want to add warnings as errors flags to this build too, but that will be covered in a separate ticket.

Definition of Done

Definition of Done is that there is a PR build in place and a dev->master build in place, building cleanly (prior to the changes being tested in that instance).

Possible Solution

  1. Create files for GCC 7.3 analogous to Trilinos/cmake/std/PullRequestLinuxGCC4.9.3TestingSettings.cmake Trilinos/cmake/std/sems/PullRequestGCC4.9.3TestingEnv.sh

and get those files into the develop branch

  1. Modify the autotester config file for dev->master testing to include this build and run the build once to detect any issues. It might be good to set up a parameterized build for 7.3 to find most issues before doing this.

  2. Once the dev->master build is clean, repeat the process at the PR level.

Assignee
Assign to
Time tracking