Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: build FreeBSD artifacts on FreeBSD 13.4 #132232

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

asomers
Copy link
Contributor

@asomers asomers commented Oct 27, 2024

13.2 is EoL, and 13.3 will be EoL too in about 2 months. Plus, both suffer from a bug in LLVM's libunwind. It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes #132185

cc @ehuss . before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
try-job: dist-various-2

@rustbot
Copy link
Collaborator

rustbot commented Oct 27, 2024

r? @GuillaumeGomez

rustbot has assigned @GuillaumeGomez.
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 rustbot added 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. labels Oct 27, 2024
@asomers
Copy link
Contributor Author

asomers commented Oct 28, 2024

@ehuss it should be ready to try now.

@ehuss
Copy link
Contributor

ehuss commented Oct 28, 2024

Hm, I'm not sure if this will work with conflicts.

@bors try

@bors
Copy link
Contributor

bors commented Oct 28, 2024

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

  1. git checkout fbsd-13.4 (switch to your branch)
  2. git fetch upstream master (retrieve the latest master)
  3. git rebase upstream/master -p (rebase on top of it)
  4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
  5. git push self fbsd-13.4 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message
Auto-merging src/doc/rustc/src/platform-support.md
CONFLICT (content): Merge conflict in src/doc/rustc/src/platform-support.md
Auto-merging src/ci/docker/scripts/freebsd-toolchain.sh
CONFLICT (content): Merge conflict in src/ci/docker/scripts/freebsd-toolchain.sh
Automatic merge failed; fix conflicts and then commit the result.

@ehuss
Copy link
Contributor

ehuss commented Oct 28, 2024

Yea, can you resolve the conflicts first?

@asomers
Copy link
Contributor Author

asomers commented Oct 28, 2024

@ehuss resolved.

@Mark-Simulacrum
Copy link
Member

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request Oct 28, 2024
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
@bors
Copy link
Contributor

bors commented Oct 28, 2024

⌛ Trying commit 4c9126d with merge 89700f8...

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Contributor

bors commented Oct 28, 2024

💔 Test failed - checks-actions

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 28, 2024
13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both
suffer from a bug in LLVM's libunwind.  It causes a segfault inside of
std::backtrace::Backtrace::capture().

Fixes rust-lang#132185
@asomers
Copy link
Contributor Author

asomers commented Oct 28, 2024

That build failure was due to a merge error. @Mark-Simulacrum @ehuss can you please try again?

@ehuss
Copy link
Contributor

ehuss commented Oct 28, 2024

@bors try

@bors
Copy link
Contributor

bors commented Oct 28, 2024

⌛ Trying commit cf34545 with merge 3b8bd37...

bors added a commit to rust-lang-ci/rust that referenced this pull request Oct 28, 2024
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
@bors
Copy link
Contributor

bors commented Oct 28, 2024

☀️ Try build successful - checks-actions
Build commit: 3b8bd37 (3b8bd37613f81d4a0b15cc3e13f5ea7aeeaf2fae)

@asomers
Copy link
Contributor Author

asomers commented Oct 28, 2024

@ehuss could you please explain to me how to download the artifacts?

@Urgau
Copy link
Member

Urgau commented Oct 28, 2024

You can use rustup-toolchain-install-master to manage try-builded toolchains.
See the usage sections for a detailed workflow.

The sha to use is the one from the build commit.

@asomers
Copy link
Contributor Author

asomers commented Oct 28, 2024

Thank you @Urgau . I am please to report that once I installed the try-built toolchain and rebuilt cargo locally, the locally-built cargo was able to build multiple projects without error, with RUST_BACKTRACE=1 .

@asomers
Copy link
Contributor Author

asomers commented Nov 1, 2024

@Urgau that works for me.

@asomers
Copy link
Contributor Author

asomers commented Jan 4, 2025

@Urgau @ehuss @Mark-Simulacrum can we merge this PR now? Now that it's 2025 ?

@Urgau
Copy link
Member

Urgau commented Jan 4, 2025

Last try was two months ago, let's see if it still works.

@bors try

@bors
Copy link
Contributor

bors commented Jan 4, 2025

⌛ Trying commit cf34545 with merge c705e8e...

bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 4, 2025
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
@bors
Copy link
Contributor

bors commented Jan 5, 2025

☀️ Try build successful - checks-actions
Build commit: c705e8e (c705e8e330e1baab7f8605649784b28da531e8b9)

@Urgau Urgau added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jan 5, 2025
@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Jan 11, 2025

📌 Commit cf34545 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 11, 2025
jhpratt added a commit to jhpratt/rust that referenced this pull request Jan 12, 2025
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 12, 2025
Rollup of 5 pull requests

Successful merges:

 - rust-lang#132232 (CI: build FreeBSD artifacts on FreeBSD 13.4)
 - rust-lang#135266 (Remove emsdk version update from 1.84.0 relnotes)
 - rust-lang#135364 (Cleanup `suggest_binding_for_closure_capture_self` diag in borrowck)
 - rust-lang#135375 (allow rustdoc-js tests to be run at stage0)
 - rust-lang#135379 (Make (unstable API) `UniqueRc` invariant for soundness)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors
Copy link
Contributor

bors commented Jan 12, 2025

⌛ Testing commit cf34545 with merge 92e74e6...

bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 12, 2025
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Contributor

bors commented Jan 12, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jan 12, 2025
@Urgau
Copy link
Member

Urgau commented Jan 12, 2025

Seems like you also need to update those lines,

AR_i686_unknown_freebsd=i686-unknown-freebsd12-ar \
CC_i686_unknown_freebsd=i686-unknown-freebsd12-clang \
CXX_i686_unknown_freebsd=i686-unknown-freebsd12-clang++ \

@Urgau
Copy link
Member

Urgau commented Jan 13, 2025

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 13, 2025
CI: build FreeBSD artifacts on FreeBSD 13.4

13.2 is EoL, and 13.3 will be EoL too in about 2 months.  Plus, both suffer from a bug in LLVM's libunwind.  It causes a segfault inside of std::backtrace::Backtrace::capture().

Fixes rust-lang#132185

cc `@ehuss` .  before you can do the trybuild, you'll also have to download new FreeBSD 13.4 base.txz images and place them in https://ci-mirrors.rust-lang.org/rustc , then update this PR with the correct file names.

try-job: dist-x86_64-freebsd
try-job: dist-various-2
@bors
Copy link
Contributor

bors commented Jan 13, 2025

⌛ Trying commit 0454d79 with merge 2a791fe...

@bors
Copy link
Contributor

bors commented Jan 13, 2025

☀️ Try build successful - checks-actions
Build commit: 2a791fe (2a791fe20bd8ecbbced38bff4be73976a7bcc14c)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

FreeBSD segfault when capturing backtrace with RUST_BACKTRACE=1
9 participants