Skip to content

Conversation

@sbomer
Copy link
Member

@sbomer sbomer commented Dec 5, 2022

@ghost
Copy link

ghost commented Dec 5, 2022

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

Issue Details

Fixes dotnet/sdk#28823.

Author: sbomer
Assignees: -
Labels:

area-NativeAOT-coreclr

Milestone: -

@sbomer sbomer requested review from LakshanF and agocke December 5, 2022 18:02
Copy link
Contributor

@LakshanF LakshanF left a comment

Choose a reason for hiding this comment

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

LGTM!

@sbomer sbomer merged commit 7ac78d2 into dotnet:main Dec 6, 2022
@agocke
Copy link
Member

agocke commented Dec 7, 2022

We only want to produce this on TFM mismatches, right? So users can get patches?

@sbomer
Copy link
Member Author

sbomer commented Dec 7, 2022

I thought about it some and I think we should be encouraging people to set RuntimeFrameworkVersion to get patches, instead of adding a packagereference. Otherwise the packagereference can specify a different version than the target runtime patch version. That's unlikely to cause issues, but when it does it could be confusing, and I'm pretty sure RuntimeFrameworkVersion is a better replacement. Thoughts?

@sbomer
Copy link
Member Author

sbomer commented Dec 7, 2022

@mangod9 how do we typically deliver patch updates to crossgen when customers hit bugs? Do we tell customers to set RuntimeFrameworkVersion for that?

@jkotas
Copy link
Member

jkotas commented Dec 7, 2022

If the fix has been released, we tell people to update the SDK that is going to update the runtime too. If we want people to try daily build before the fix is released, https://github.com/dotnet/runtime/blob/main/docs/project/dogfooding.md#advanced-scenario---using-a-daily-build-of-microsoftnetcoreapp has the instructions. These instructions apply to any runtime fix, they are not crossgen specific.

@agocke
Copy link
Member

agocke commented Dec 7, 2022

That’s a good point, I forgot we could recommend using nighties.

I’m fine with that approach instead.

@sbomer
Copy link
Member Author

sbomer commented Dec 21, 2022

/backport to release/7.0

@github-actions
Copy link
Contributor

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3745285250

@github-actions
Copy link
Contributor

@sbomer backporting to release/7.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Prevent warning for implicit ILCompiler reference
Using index info to reconstruct a base tree...
M	src/coreclr/nativeaot/BuildIntegration/Microsoft.DotNet.ILCompiler.SingleEntry.targets
Falling back to patching base and 3-way merge...
Auto-merging src/coreclr/nativeaot/BuildIntegration/Microsoft.DotNet.ILCompiler.SingleEntry.targets
CONFLICT (content): Merge conflict in src/coreclr/nativeaot/BuildIntegration/Microsoft.DotNet.ILCompiler.SingleEntry.targets
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Prevent warning for implicit ILCompiler reference
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

@sbomer an error occurred while backporting to release/7.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@ghost ghost locked as resolved and limited conversation to collaborators Jan 20, 2023
@sbomer sbomer deleted the fixPackageWarning branch November 3, 2023 18:37
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.

PublishAot warning with net8.0

4 participants