🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/143979

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 52dea10 with merge base 33a1996 ():

This comment was automatically generated by Dr. CI and updates every 15 minutes.

Hi, @malfet

Here’s a gentle ping: we have fixed some code errors detected by the CI. When you have time, could you please take a look and provide any suggestions?

@Skylion007 Could you help review it if you have time?

@malfet @Skylion007

@zhangfeiv0 Do you mind changing it to opt-in only for now and delete binary wheels workflow? Let's see if builds are passing first and than we can take next steps.

@pytorchbot rebase

Unknown label ciflow/riscv64.
Currently recognized labels are

• ciflow/binaries
• ciflow/binaries_libtorch
• ciflow/binaries_wheel
• ciflow/inductor
• ciflow/inductor-periodic
• ciflow/inductor-rocm
• ciflow/inductor-perf-compare
• ciflow/inductor-micro-benchmark
• ciflow/inductor-micro-benchmark-cpu-x86
• ciflow/inductor-cu126
• ciflow/linux-aarch64
• ciflow/mps
• ciflow/nightly
• ciflow/periodic
• ciflow/rocm
• ciflow/s390
• ciflow/slow
• ciflow/trunk
• ciflow/unstable
• ciflow/xpu
• ciflow/torchbench
• ciflow/autoformat

@pytorchbot rebase

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Successfully rebased riscv_ci_support onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout riscv_ci_support && git pull --rebase)

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Tried to rebase and push PR #143979, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

Making some changes to the workflow now. If it finished build in reasonable amount of time, than yes, it could be landed as an opt-in for now

@zhangfeiv0, you'll need to adapt your PR to make it work with CI build, i.e. docker for CI is build using files in .ci/docker folder, rather than in .ci/docker/manywheel, and are stored on ECR/ghcr.io rather than on docker hub

Successfully rebased riscv_ci_support onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout riscv_ci_support && git pull --rebase)

During cross-compilation, some third-party libraries need to run on the host machine, including protocbuf and sleef.

• Protobuf: As per your suggestion, it was disabled.
• Sleef: Still requires execution on the host machine during compilation.

To address this, I introduced docker/setup-qemu-action@v3 to emulate the execution of the necessary binaries in these third-party libraries. This approach was also tested in my local environment. However, in the last workflow run, the protobuf binary failed to execute, suggesting this solution did not work as intended.
I moved this step into the Build step to see if it resolves the issue. If successful, this would eliminate the need to disable protobuf.

Additionally, some steps you previously deleted need to be retained; otherwise, compilation errors will still occur during the build phase.

@malfet Could you restart the workflow and check again? Thanks!

@malfet bump!

Shall we rebase this again? @zhangfeiv0

@houseroad Friendly ping