Cicd combined#95
Conversation
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Ruff loads its config from pyproject.toml, so a malformed pyproject.toml makes ruff abort with a parser error instead of the clean check-toml message. Running check-toml/check-yaml first (with fail_fast) ensures syntax errors are reported by the dedicated validator, consistently between local commits and CI's --all-files run. Signed-off-by: aviv ron <rona@il.ibm.com>
check-added-large-files only inspects staged additions, so on CI's clean checkout (nothing staged) it was a no-op. --enforce-all makes it check all files under pre-commit run --all-files. uv.lock (~2.3 MB) is excluded as an intentionally large lockfile. Signed-off-by: aviv ron <rona@il.ibm.com>
check-merge-conflict returns early unless a merge is in progress, so on CI's clean checkout it was a no-op. --assume-in-merge makes it always scan, letting pre-commit run --all-files catch committed conflict markers. Signed-off-by: aviv ron <rona@il.ibm.com>
…hooks Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
uv lock resolves fine on macOS; only installing the vLLM/CUDA wheels fails. --frozen is for not mutating the lock, not because a re-resolve would fail. Also note the uv-lock pre-commit hook runs locally. Signed-off-by: aviv ron <rona@il.ibm.com>
CI's coverage run executes only tests/unit/, which exercises just the pure-Python config module. Measuring the whole granite_switch package diluted the reported coverage to ~1%, because the hf/vllm/composer/ tutorials subpackages are GPU/model-only and unreachable in CI. Add [tool.coverage.run] omit rules for those subpackages so the CI coverage number reflects the code the unit suite is actually responsible for (now ~96%). Full-project coverage continues to be measured on the GPU cluster. Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
Signed-off-by: aviv ron <rona@il.ibm.com>
PR ReviewStrong infrastructure PR overall — the CI/CD direction looks good and the pre-commit/dev-experience improvements are valuable. What looks good
Requested changes
Nits
Overall: good direction, but I’d request the DCO fix and clearer CI/test-coverage expectations before merge. |
| # git config blame.ignoreRevsFile .git-blame-ignore-revs | ||
|
|
||
| # Apply ruff format and lint autofixes across the codebase | ||
| e1a92ceab87dc0ab6517916954a430d16b2da1b6 |
There was a problem hiding this comment.
As we squash the commits this wouldn't work for the current PR, we can either (1) squash the commits as part of the changes so that there is a single commit in this PR, (2) after we merge this PR, open a new PR only for the blame ignore with the squash commit
There was a problem hiding this comment.
@antonpibm In that case, I suggest we split this PR into two parts.
First - only the ruff formatting changes - this one needs to be ignored in git blame.
Second - after we merged the first, merge the CICD work - this should not get ignored by git blame since it is authentic development work, and not a reformat.
we can insert also the git blame ignore revs with the new sha after the first pr merge into the second pr.
Technically it is not complicated to aheieve since the reformat commit was the first commit in this branch, so I can easily split it into two.
If you agree, I will do it.
antonpibm
left a comment
There was a problem hiding this comment.
Please see the minor comments
….0 MVP - Shorten CLAUDE.md pre-commit section to a brief blurb pointing at the CI/CD reference doc - Rename docs/CICD_PLAN.md -> docs/CICD.md as the living reference; retitle and fix the reference in pyproject.toml - Change CHANGELOG 0.1.0 from Pre-release to MVP Signed-off-by: aviv ron <rona@il.ibm.com>
Fold the DCO / Signed-off-by requirement into GIT_WORKFLOW.md so the sign-off steps live alongside the branching and commit guidance, with a pointer to CICD.md for the full hook and CI setup. Signed-off-by: aviv ron <rona@il.ibm.com>
No description provided.