Skip to content

Fail tests if LTCG is used #111651

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

Merged
merged 5 commits into from
Feb 3, 2025
Merged

Conversation

MichalStrehovsky
Copy link
Member

#111566 is not the first time we accidentally shipped something built with LTCG. We should ideally not allow merging such code into main.

Cc @dotnet/ilc-contrib

dotnet#111566 is not the first time we accidentally shipped something built with LTCG. We should ideally not allow merging such code into `main`.
Copy link
Contributor

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

@jkotas
Copy link
Member

jkotas commented Jan 21, 2025

/azp run runtime-nativeaot-outerloop

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkotas
Copy link
Member

jkotas commented Jan 21, 2025

I assume that we should see this failing (in outer loop at least) until #111566 gets fixed. Is that right?

@jkotas
Copy link
Member

jkotas commented Jan 21, 2025

I assume that we should see this failing (in outer loop at least) until #111566 gets fixed. Is that right?

It does not appear to be failing as expected.

@MichalStrehovsky
Copy link
Member Author

I assume that we should see this failing (in outer loop at least) until #111566 gets fixed. Is that right?

Yep, it was supposed to fail. Operator error.

@MichalStrehovsky MichalStrehovsky added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Jan 22, 2025
@MichalStrehovsky
Copy link
Member Author

Yup, now failing as expected. Marked as no merge until #111566 is fixed.

@MichalStrehovsky MichalStrehovsky removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants