V2.7.1 分支提供依赖镜像#138
Conversation
Add .ci/docker/ directory with separated builder (manylinux) and test (ubuntu) images for both x86_64 and aarch64 architectures. - Builder images: PyTorch + build toolchain (gcc, cmake, ninja, mold, ccache) - Test images: PyTorch CPU + CANN runtime + triton-ascend + test frameworks - CANN chip selection via CANN_CHIP build arg (A1/A2/A3) - docker_build.sh follows upstream pytorch/pytorch tag parsing pattern - GitHub Actions workflow for building and pushing to quay.io Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Docker tags must be lowercase. Tag format changed from cannA1 to cann-a1, while CANN_CHIP build arg stays uppercase (A1/A2/A3) for install_cann.sh. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
requirements-*.txt files are at the docker context root, not in common/. Add explicit COPY instructions in all four Dockerfiles. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Builder images no longer install CANN/OBS, so COPY common/ is not needed. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
PyTorch is arch-specific (torch==2.7.1+cpu for x86_64, torch==2.7.1 for aarch64). Installing directly in Dockerfile avoids pip env-var expansion issues with requirements files. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…mmands - workflow_dispatch now accepts optional 'tag' to build a single image - summary job collects results via artifacts and outputs docker pull commands Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
GitHub Actions outputs must be single-line. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…n test Dockerfiles
…input from build workflow
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…N_VERSION in top-level workflow - Move docker_image_build and docker_image_test to top-level workflow inputs with defaults - Remove pytorch_version from all workflow inputs, hardcode as env.PYTORCH_VERSION=2.7.1 - Remove python_version from trigger/top-level inputs, hardcode as env.PYTHON_VERSION=3.10 - Pass docker_image to build workflow instead of hardcoding in container definition - Update all sub-workflows to remove pytorch_version input parameter
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…ith: section env context is not available in with: section of reusable workflow calls
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
- Replace hardcoded Ascend/pytorch action ref with ./.github/actions/setup-npu-test-env - Add pytorch_version and python_version as workflow inputs in top-level test workflow - Remove unused env.PYTORCH_VERSION from build workflow Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…kflows - Remove unused pyyaml from builder, beartype/attrs/decorator from test deps - Change local action ref to fork repo ref to fix PR checkout issue: `./.github/actions/setup-npu-test-env` -> `kerer-ai/pytorch/.github/actions/setup-npu-test-env@v2.7.1_image` Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…ll_cases.py Log LD_LIBRARY_PATH, libhccl.so location, CANN version at two levels: - Workflow: before running collect script - Python: appended to error output on pytest collection failure Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…ioned paths A3 CANN 9.0.0-beta.2 installs to versioned directory, not /usr/local/Ascend/cann/ Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
.diff 文件命名格式为 test_foo.diff（不含 .py）， 需将 .diff 替换为 .py 而非直接去掉后缀。 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
1 similar comment
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
GitHub Actions 平台自动注入 CI=true，会触发 PyTorch 测试文件中 IS_CI 条件分支跳过用例生成。在三个测试 workflow 的 step 层 以 CI: '' 覆盖平台默认值。 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
test_upstream/test/ 是给源码测试文件打的 patch， test_upstream/torch/ 是给已安装 torch 包打的 patch， 由 torch_env_patch.sh 负责。原脚本 find 扫描整个 test_upstream/ 会导致 torch/ 下的环境 patch 被错误打到源码上。 Ref: https://gitcode.com/Ascend/pytorch/pull/37974 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Add all signal crash (SIGSEGV/SIGABRT/SIGKILL/SIGBUS) and timeout cases from reg-1 through reg-5 shards in CI run 27246250974. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Add 51 new entries covering all non-signal-crash errors (rc=4 No testcase in XML, rc=1 setup failures/no result) and remaining cases from CI run 27246250974. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Covers teardown FileNotFoundError, TORCH_LIBRARY conflicts, Ninja missing, and other framework-level errors from CI. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
When the pipeline is triggered by schedule/workflow_dispatch on master, github.sha points to a master commit which lacks test_upstream/ and may have different torch_npu source. Use v2.7.1 ref in that case, otherwise use github.sha for PR-triggered runs on v2.7.1. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
When test worker output contains valid JSON that is not a dict (e.g. arrays, strings), save the full content to unexpected_stdout/ for debugging instead of silently discarding it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
…configs - Report: update --runner string to reflect a3-8 for distributed, a3-16 for custom, and 16 workers for regular (not 64) - Collect: update echo logs to match actual runner/worker configuration Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
每次reg和dist测试完成后将 /root/ascend 打包为 tar.gz 并上传到 制品，方便后续排查 CANN 底层报错问题。 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CLA Signature Guide@kerer-ai , thanks for your pull request. The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
To sign CLA, click here. To check if your email is configured correctly, refer to the FAQs. Once you've signed the CLA or updating your email, please comment |
2 participants
No description provided.