-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
add some debug-assertion crash tests #132789
base: master
Are you sure you want to change the base?
Conversation
@bors try |
add some debug-assertion crash tests r? ghost try-job: x86_64-gnu-llvm-18
@rustbot author |
☀️ Try build successful - checks-actions |
r? @jieyouxu |
b521cae
to
3a2c247
Compare
//@ needs-rustc-debug-assertions | ||
|
||
#![feature(dyn_star)] | ||
#![allow(incomplete_features)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question/discussion: should we even add crashes tests for incomplete features...? Cuz like, it's known to be incomplete, right? I feel like we should just backlink the bug report to the tracking issue (and tag it along with the github subissues thing), because otherwise if someone wants to drive dyn_star
forward a crashes test might just be friction idk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, I'm inclined to r+ this because crashes tests are easy to remove and helps to detect changes (incl. fixes). Whether to add incomplete_features crashes tests in the future can be discussed separately.
@bors r+ rollup=iffy |
add some debug-assertion crash tests r? ghost try-job: x86_64-gnu-llvm-18
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Hm, that's weird... Is the directive implementation wrong I wonder EDIT: I'm missing something because this passes locally and is ignored when rustc built without debug assertions as I expected. |
It doesn't even fail locally in |
@bors try |
add some debug-assertion crash tests r? ghost try-job: x86_64-gnu
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
r? ghost
try-job: x86_64-gnu