Skip to content

Cicd combined#95

Draft
aviv1ron1 wants to merge 21 commits into
generative-computing:mainfrom
aviv1ron1:cicd-combined
Draft

Cicd combined#95
aviv1ron1 wants to merge 21 commits into
generative-computing:mainfrom
aviv1ron1:cicd-combined

Conversation

@aviv1ron1

Copy link
Copy Markdown
Collaborator

No description provided.

aviv1ron1 added 11 commits July 9, 2026 15:22
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>
@codecov-commenter

Copy link
Copy Markdown

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 ☂️

aviv1ron1 added 10 commits July 9, 2026 21:39
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants