-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Add new tool for dumping feature status based on tidy #135844
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
May need to rebase the merge commit away (maybe this is a different set of changes?) |
yeah I realized that this was a branch named after your branch but which I failed to merge into when I was trying to sort out the commit history stuff, then when I pushed this I took a break because I've been feeling like shit this week and had to rest. Thank you for being so patient with me. |
b78ca32
to
a542953
Compare
This comment has been minimized.
This comment has been minimized.
bd19bac
to
69b79a3
Compare
alright, I think we're gucchi. I haven't tested it but hopefully CI will do that, gotta run and catch a train. |
This comment has been minimized.
This comment has been minimized.
69b79a3
to
f5dff8d
Compare
Co-authored-by: Jane Losare-Lusby <jlusby42@gmail.com>
Co-authored-by: Jane Losare-Lusby <jlusby42@gmail.com>
And also register its check step. Co-authored-by: Jane Losare-Lusby <jlusby42@gmail.com>
f5dff8d
to
cbcba57
Compare
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.
The changes looked good to me, so I checked out your branch locally to test. Only two tiny issues that I needed to change to get the check and run steps to work properly, so I pushed the fix to your branch (and slightly adjusted the commit history). Let me know what you think, otherwise r=me and you.
With the two fixes to get it to build, I tested these locally:
./x check src/tools/features-status-dump
... OK./x check src/tools/features-status-dump
(unmodified re-run)... OK./x check src/tools/features-status-dump
(modified)... OK, REBUILDS./x run src/tools/features-status-dump
... OK, produces a JSON underbuild/
./x run src/tools/features-status-dump
(modified)... OK, REBUILDS
Not sure why it still said |
Hey no worries, take it easy, there's no rush. I hope you feel better soon :3 |
lgtm, thank you for the fixup ^_^ @bors r=jieyouxu |
Rollup of 5 pull requests Successful merges: - rust-lang#134777 (Enable more tests on Windows) - rust-lang#135621 (Move some std tests to integration tests) - rust-lang#135844 ( Add new tool for dumping feature status based on tidy ) - rust-lang#136167 (Implement unstable `new_range` feature) - rust-lang#136334 (Extract `core::ffi` primitives to a separate (internal) module) Failed merges: - rust-lang#136201 (Removed dependency on the field-offset crate, alternate approach) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#135844 - yaahc:tidy-feature-status-dump, r=jieyouxu Add new tool for dumping feature status based on tidy sequel to rust-lang#133514 meaning ... supercedes rust-lang#133351 part of rust-lang#129485 r? `@jieyouxu` cc `@estebank`
Rollup of 5 pull requests Successful merges: - rust-lang#134777 (Enable more tests on Windows) - rust-lang#135621 (Move some std tests to integration tests) - rust-lang#135844 ( Add new tool for dumping feature status based on tidy ) - rust-lang#136167 (Implement unstable `new_range` feature) - rust-lang#136334 (Extract `core::ffi` primitives to a separate (internal) module) Failed merges: - rust-lang#136201 (Removed dependency on the field-offset crate, alternate approach) r? `@ghost` `@rustbot` modify labels: rollup
sequel to #133514
meaning ...
supercedes #133351
part of #129485
r? @jieyouxu
cc @estebank