You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[需求] 支持细粒度的NPU使用率采集(runner-container-hooks)· 开发流水线 · 开发预览阶段(代码已推 + 预览已部署 + UT 已补;门禁/对抗由 PR CI 异步跑)
改动内容
fix(ascend-ci-deployment): fix yamllint failures across kustomization.yaml files
Fixed all yamllint errors in the ascend-ci-deployment submodule that were
blocking the deterministic gate. The provided failure list was truncated;
a full yamllint run revealed 30 files with errors (29 kustomization.yaml
1 prometheus-rules.yaml).
Changes:
Indentation fix (29 kustomization.yaml files): Added 2-space
indentation to all list items (lines starting with - at column 0)
under resources: and patches: keys, per .yamllint config
(indentation: indent-sequences: true). Commented-out list items
(starting with #) were left untouched.
Empty-lines fix: Removed trailing blank lines at end of file in files
that had max-end: 0 violations. Ensured exactly one trailing newline
per file.
new-line-at-end-of-file fix: monitoring/config-for-ascend-triton-agent-ci/kustomization.yaml was
missing a trailing newline — added one.
line-length fix: monitoring/config-for-infra-cn4-x86-common-cluster/prometheus-rules.yaml
line 1233 was 239 chars (>200 limit). Split the long description:
string across 3 lines using YAML \ continuation, matching the existing
pattern used elsewhere in the same file (e.g. lines 857-859, 943-945).
Test fix: Updated tests/test_vllm_omni_buildkite.py — TestConfigGy003.test_kustomization_resources and TestConfigSh001.test_kustomization_resources were expecting 3
resources but the kustomization.yaml files now include npu-metrics-pushgw-secret.yaml (added in issue-1968 round 1/2).
Added the missing resource to the expected sorted list in both tests.
Verification:
yamllint -c .yamllint on all 205 changed YAML files: 0 errors
python3 -m pytest tests/ (excluding pre-existing broken
test_sync_new_projects_to_docs.py which references a non-existent script):
175 passed
python3 scripts/check-projects-coverage.py: passes (no new dirs to check)
No UT files added — this round is pure YAML formatting + test expectation
fix; no business logic changes.
Hey @fly333sky , thanks for your contribution to the community.
Bot Usage Manual
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
[需求] 支持细粒度的NPU使用率采集(runner-container-hooks)· 开发流水线 · 开发预览阶段(代码已推 + 预览已部署 + UT 已补;门禁/对抗由 PR CI 异步跑)
改动内容
fix(ascend-ci-deployment): fix yamllint failures across kustomization.yaml files
Fixed all yamllint errors in the ascend-ci-deployment submodule that were
blocking the deterministic gate. The provided failure list was truncated;
a full yamllint run revealed 30 files with errors (29 kustomization.yaml
Changes:
Indentation fix (29 kustomization.yaml files): Added 2-space
indentation to all list items (lines starting with
-at column 0)under
resources:andpatches:keys, per.yamllintconfig(
indentation: indent-sequences: true). Commented-out list items(starting with
#) were left untouched.Empty-lines fix: Removed trailing blank lines at end of file in files
that had
max-end: 0violations. Ensured exactly one trailing newlineper file.
new-line-at-end-of-file fix:
monitoring/config-for-ascend-triton-agent-ci/kustomization.yamlwasmissing a trailing newline — added one.
line-length fix:
monitoring/config-for-infra-cn4-x86-common-cluster/prometheus-rules.yamlline 1233 was 239 chars (>200 limit). Split the long
description:string across 3 lines using YAML
\continuation, matching the existingpattern used elsewhere in the same file (e.g. lines 857-859, 943-945).
Test fix: Updated
tests/test_vllm_omni_buildkite.py—TestConfigGy003.test_kustomization_resourcesandTestConfigSh001.test_kustomization_resourceswere expecting 3resources but the kustomization.yaml files now include
npu-metrics-pushgw-secret.yaml(added in issue-1968 round 1/2).Added the missing resource to the expected sorted list in both tests.
Verification:
yamllint -c .yamllinton all 205 changed YAML files: 0 errorspython3 -m pytest tests/(excluding pre-existing brokentest_sync_new_projects_to_docs.py which references a non-existent script):
175 passed
python3 scripts/check-projects-coverage.py: passes (no new dirs to check)No UT files added — this round is pure YAML formatting + test expectation
fix; no business logic changes.
相关 Issue
resolve https://github.com/opensourceways/backlog/issues/1968
AI 使用声明
当前 PR 是否有 AI 参与:
/ai-develop-preview