ci: Enable full debuginfo-level=2 in DEPLOY_ALT

[cuviper]

It will be slower to build and produce larger artifacts, but hopefully
it will help catch debuginfo regressions sooner, especially for problems
that LLVM assertions would uncover.

try-job: dist-x86_64-linux
try-job: dist-x86_64-linux-alt

[rustbot]

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

[cuviper]

I expect the alt build to fail on #131944.

@bors try

[bors]

⌛ Trying commit dd47d77 with merge 3e142fb...

[bors]

💔 Test failed - checks-actions

[cuviper]

rustc: /checkout/src/llvm-project/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:303: void llvm::Loc::MMI::addFrameIndexExpr(const DIExpression *, int): Assertion `(FrameIndexExprs.size() == 1 || llvm::all_of(FrameIndexExprs, [](const FrameIndexExpr &FIE) { return FIE.Expr && FIE.Expr->isFragment(); })) && "conflicting locations for variable"' failed.
[RUSTC-TIMING] cargo test:false 246.899
rustc exited with signal: 6 (SIGABRT) (core dumped)

@rustbot blocked

[cuviper]

Added #131944 (comment)

@bors try

[bors]

⌛ Trying commit 61cd0c7 with merge 28380af...

[bors]

☀️ Try build successful - checks-actions
Build commit: 28380af (28380af8632392dcbf5153473388955f46275aee)

[wesleywiser]

Hi @cuviper, it looks like the alt builds succeeded this time. Should we try to land this?

[cuviper]

I would be ok with landing this, especially if you want to give that added fix a review.

@rustbot ready

It would be nice to have a more targeted test too, like #131944 (comment) -- but I don't know if we can use real crate dependencies in our testsuite.

[jieyouxu]

It would be nice to have a more targeted test too, like #131944 (comment) -- but I don't know if we can use real crate dependencies in our testsuite.

You can in run-make tests to invoke cargo to build an external crate... as long as that doesn't take an unreasonable amount of time.

[cuviper]

I would also want to be sure that external crate still pulls from vendored sources in offline builds -- but anyway #132613 should be a more proper fix, and then I'll drop the patch here and rebase the CI change alone.

[jieyouxu]

I would also want to be sure that external crate still pulls from vendored sources in offline builds -- but anyway #132613 should be a more proper fix, and then I'll drop the patch here and rebase the CI change alone.

Yeah, this is indeed a problem cf. #128733

[cuviper]

@bors try

[bors]

⌛ Trying commit fc83c8a with merge 8c5da65...

[bors]

☀️ Try build successful - checks-actions
Build commit: 8c5da65 (8c5da6539d0ddeedb04c64efc8d7636fb3641280)

[cuviper]

@Mark-Simulacrum -- this is ready for review as a pure CI change now.

It will be slower to build and produce larger artifacts,

Somehow it was actually faster than its parent build, but that's probably noise. The size is quite significant though, using rustup-toolchain-install-master --alt.

• parent commit de27914e8e6c5f8a02698a8ed9b318df17f2f621
  • built in 2h 16m 10s: https://github.com/rust-lang-ci/rust/actions/runs/11782098078/job/32816399563
  • downloaded 88.92 MiB rustc and 29.78 MiB std, for 506.64 MiB installed
• try commit 8c5da6539d0ddeedb04c64efc8d7636fb3641280
  • built in 2h 7m 36s: https://github.com/rust-lang-ci/rust/actions/runs/11786263781/job/32829211877
  • downloaded 236.42 MiB rustc and 37.68 MiB std, for 1.61 GiB installed

[cuviper]

If we don't want to affect DEPLOY_ALT, we could instead try increasing debug in some other llvm-asserting CI job.

[Mark-Simulacrum]

@bors r+

I'm fine increasing the size of alt builds, that seems unlikely to break anyone. We can revert if we hit problems.

[bors]

📌 Commit fc83c8a has been approved by Mark-Simulacrum

It is now in the queue for this repository.