Skip to content

Conversation

dianqk
Copy link
Member

@dianqk dianqk commented Oct 9, 2025

Fixes #146742.

After #146124, we need more space to run x86_64-gnu-distcheck if building LLVM from source. According to the building log, the space freed by free-disk-space-linux.sh is not entirely available.

You are running out of disk space. 
The runner will stop working when the machine runs out of disk space. 
Free space left: 98 MB

disk usage:
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        72G   43G   29G  60% /
tmpfs           7.9G   84K  7.9G   1% /dev/shm
tmpfs           3.2G  1.2M  3.2G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda16      881M   60M  760M   8% /boot
/dev/sda15      105M  6.2M   99M   6% /boot/efi
/dev/sdb1        74G   28K   70G   1% /mnt
tmpfs           1.6G   12K  1.6G   1% /run/user/1001

@rustbot rustbot added A-CI Area: Our Github Actions CI A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Oct 9, 2025
@dianqk
Copy link
Member Author

dianqk commented Oct 9, 2025

@bors try jobs=x86_64-gnu-distcheck

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Oct 9, 2025
Update LLVM to 21.1.3

try-job: x86_64-gnu-distcheck
@rust-log-analyzer

This comment has been minimized.

@rust-bors
Copy link

rust-bors bot commented Oct 9, 2025

💔 Test for d6659ce failed: CI. Failed jobs:

@rustbot rustbot added the A-testsuite Area: The testsuite used to check the correctness of rustc label Oct 9, 2025
@dianqk
Copy link
Member Author

dianqk commented Oct 9, 2025

@bors try jobs=x86_64-gnu-distcheck

rust-bors bot added a commit that referenced this pull request Oct 9, 2025
Update LLVM to 21.1.3

try-job: x86_64-gnu-distcheck
@rust-bors

This comment has been minimized.

@dianqk dianqk marked this pull request as ready for review October 9, 2025 15:25
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 9, 2025
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Oct 9, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 9, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot
Copy link
Collaborator

rustbot commented Oct 9, 2025

⚠️ Warning ⚠️

@rust-bors
Copy link

rust-bors bot commented Oct 9, 2025

☀️ Try build successful (CI)
Build commit: bfdd4ca (bfdd4ca14dcc7a1a42c76b7c45521bde578bc92c, parent: acf243778e6c54cb7d54bee4be88e510e4be123e)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: Our Github Actions CI A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Matching on enums with optimizations enabled causes rustc-LLVM errors on the nvptx64-nvidia-cuda target
4 participants