Conversation
|
if we go this route we should also leave some breadcrumbs in the code to know when we can revert the changes too It might make more sense to just fix the upstream bug |
I believe that we want to enable this regardless of the upstream bug fixes, because this is about preventing further debug-assertion-failures from landing. |
|
+1 from me, I just raised this issue with @andygrove on Comet today when we are adding I love |
|
This did not fail because But this PR will/should fail until the arrow upgrade fix for #20689 is actually merged. |
Yea, it looks like you are right: https://doc.rust-lang.org/cargo/reference/profiles.html#dev I'm happy to remove it, or to leave it explicit. |
Which issue does this PR close?
main#20831.Rationale for this change
CI uses release profiles to allow tests to run more quickly (and potentially also to provide more coverage for the most realistic case for end users of the system). But debug assertions can expose real bugs / mistaken assumptions, and so they should be covered in CI as well.
What changes are included in this PR?
Adjust the Rust build profiles which are used in CI to enable debug assertions. Split out a
ci-releaseprofile fromreleasein order to avoid shipping debug assertions to end users of the CLI tool.Are these changes tested?
Yes, by CI.
Are there any user-facing changes?
No.