Skip to content

测试#113

Open
kerer-ai wants to merge 14 commits intoAscend:masterfrom
kerer-ai:master
Open

测试#113
kerer-ai wants to merge 14 commits intoAscend:masterfrom
kerer-ai:master

Conversation

@kerer-ai
Copy link
Copy Markdown
Collaborator

@kerer-ai kerer-ai commented Apr 2, 2026

测试

kerer-ai and others added 8 commits March 6, 2026 16:57
This workflow:
1. Clones PyTorch main repository
2. Clones kerer-ai/pytorch repository
3. Builds PyTorch from source
4. Builds torch_npu extension
5. Tests the installation
6. Uploads build artifacts

The workflow supports multiple Python versions (3.9, 3.10, 3.11)
and can be triggered on push to master, pull requests, or manually.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Changes:
1. Remove torch installation from requirements.txt to avoid conflict with compiled PyTorch
2. Add Huawei Cloud mirror for faster package installation in China
3. Add warning about missing CANN environment
4. Adjust Python versions to match existing CI (3.8, 3.9, 3.10)

The build may still fail due to missing CANN drivers for Ascend NPU support.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This workflow only checks:
1. Build script syntax
2. setup.py syntax
3. Project structure

It does not attempt full build, which requires CANN environment.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1. build-pytorch.yml: Builds PyTorch from source
   - Supports multiple Python versions (3.9, 3.10, 3.11)
   - Two build modes: develop (editable) and install
   - Weekly scheduled builds

2. build-torch-npu-simple.yml: Simplified torch_npu build
   - Installs pre-built PyTorch
   - Checks environment and dependencies
   - Creates build report with next steps
   - Acknowledges CANN dependency requirement

These workflows separate the complex build process and provide
better debugging information.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This workflow:
1. Installs the exact PyTorch version required (2.11.0.dev20251215)
2. Includes numpy to avoid warnings
3. Provides detailed analysis of build requirements
4. Documents CANN dependency clearly

The build still requires CANN environment for Ascend NPU support.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
9fbb5b19 Add GitHub Actions workflow for ... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.
7e7cbdc3 添加构建 the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@kerer-ai
Copy link
Copy Markdown
Collaborator Author

kerer-ai commented Apr 2, 2026

/check-cla

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
9fbb5b19 Add GitHub Actions workflow for ... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.
7e7cbdc3 添加构建 the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@kerer-ai
Copy link
Copy Markdown
Collaborator Author

kerer-ai commented Apr 3, 2026

/check-cla

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

@ascend-robot
Copy link
Copy Markdown

CLA Signature Guide

@kerer-ai , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
4e67e9db Merge branch 'Ascend:master' int... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the 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 /check-cla to revalidate CLA status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants