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

Classify FIXMEs - 6 #4234

Merged
merged 1 commit into from
Feb 23, 2025
Merged

Classify FIXMEs - 6 #4234

merged 1 commit into from
Feb 23, 2025

Conversation

lvllvl
Copy link
Contributor

@lvllvl lvllvl commented Jan 6, 2025

Description

Responding to #4117, added labels to all FIXMEs in repo. Breaking this up into multiple PRs for review.

Sources

Checklist

  • Relevant tests in libc-test/semver have been updated
    • Not applicable
  • No placeholder or unstable values like *LAST or *MAX are
    included (see #3131)
  • Tested locally (cd libc-test && cargo test --target mytarget);
    especially relevant for platforms that may not be checked in CI
    • Not applicable

@rustbot
Copy link
Collaborator

rustbot commented Jan 6, 2025

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @tgross35 (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

  • @rustbot author: the review is finished, PR author should check the comments and take action accordingly
  • @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

@@ -680,7 +680,7 @@ fn test_windows(target: &str) {
// Just pass all these through, no need for a "struct" prefix
"FILE" | "DIR" | "Dl_info" => ty.to_string(),

// FIXME: these don't exist:
// FIXME(ctest): these don't exist:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// FIXME(ctest) should be for things that fail due to bugs in ctest itself (i.e. need to be fixed in the ctest crate), rather than things that fail while running ctest. So this could probably just get the relevant platform, FIXME(windows).

Couple instances of ctest here but the rest lgtm 👍 . Please squash and rebase after updating those.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok sounds good. This should be resolved now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like there is one more, // FIXME(ctest): The size and alignment of this struct are incorrect (line 725). The rest lgtm 👍

@tgross35
Copy link
Contributor

@lvllvl could you change the last FIXME(ctest): The size and alignment of this struct are incorrect to FIXME(windows)? From #4234 (comment)

@lvllvl lvllvl force-pushed the 4117-part-6 branch 3 times, most recently from 40b5d60 to 835192e Compare February 22, 2025 23:12
@lvllvl
Copy link
Contributor Author

lvllvl commented Feb 23, 2025

@lvllvl could you change the last FIXME(ctest): The size and alignment of this struct are incorrect to FIXME(windows)? From #4234 (comment)

Hi, yes just made the updates. If there's any other change please let me know. I think there's 2 other PRs that I need to wrap up. Will try and address those tomorrow.

Copy link
Contributor

@tgross35 tgross35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updates, looks great!

@tgross35 tgross35 added this pull request to the merge queue Feb 23, 2025
Merged via the queue into rust-lang:main with commit 6e0ee6f Feb 23, 2025
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants