NWChemEx / NWChemEx/.github

CI Build Settings

Open
#12 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
1
Forks
2
Avg merge
22m
Merged PRs (30d)
4

Description

I have repurposed this issue somewhat. The original intent was basically to get the build to be warning free. If our CI build enables warnings and converts the warnings to errors, we accomplish the same thing. The CMake solution described in the original issue would still help developers test for warnings locally, but is independent of CI.

The second part of this issue is to actually get the code to be warning free so that it passes the aforementioned CI...

Original issue:

I think it would be useful to define a CMake module (that is synchronized across the NWX repos) with build-type settings. For example:

  • release should be O3 with warnings disabled
  • debug should have all warnings enabled (and possibly converted to errors)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the organization’s CI configuration and the proposed shared CMake build-type settings across the NWX repositories. Check how debug and release builds currently handle warnings, then identify the warnings that prevent CI from passing. Done means the relevant CI builds are warning-free and the CMake settings support the described local warning checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake
Domain
build-system, ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.