Skip to content

GitLab

  • Menu
Projects Groups 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
    • 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
  • #924

Closed
Open
Created Dec 13, 2016 by James Willenbring@jmwilleOwner

Work-around (not a bug) for recent changes to check-in test script

Created by: mhoemmen

I discussed this with @maherou , and he agreed that it would be helpful for me to post these instructions, as a way to smooth the eventual transition to a pull request model.

Suppose that you were using the (old) check-in test script before. The #482 (closed) fix broke this process. If you want your old check-in test scripts to work, you'll need to do the following:

  1. Change path to internal check-in.py script: ${TRILINOS_PATH}/cmake/tribits/ci_support/checkin-test.py (replace ${TRILINOS_PATH} with path to your Trilinos source directory)

  2. Add the following arguments to the script: --default-builds="" –extra-builds=MPI_DEBUG,SERIAL_RELEASE (this removes that MPI_RELEASE_DEBUG_* build and replaces it with the old builds, and also enables all packages, not just Primary Tested)

Assignee
Assign to
Time tracking