-
Notifications
You must be signed in to change notification settings - Fork 4.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
[release/8.0] Manually update release/8.0 arcade to latest #92778
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsArcade flow is stuck somewhere in release/8.0 this the result of running cc @ViktorHofer
|
cc @ericstj |
@sbomer I assume this is fixed via dotnet/sdk#35767 ? |
No, dotnet/sdk#35767 won't fix this instance because it was caused by setting |
Now seeing errors like
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsArcade flow is stuck somewhere in release/8.0 this the result of running
|
@elinor-fung are the host failures here rid related? |
@@ -1,16 +1,16 @@ | |||
{ | |||
"sdk": { | |||
"version": "8.0.100-preview.7.23376.3", | |||
"version": "8.0.100-rc.1.23455.8", |
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.
@lewing Should this be rtm? Also the one below.
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.
Just asking because we've been doing similar manual adjustments in wasm flows. I don't know if it applies to this as well.
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.
Not yet, we have to wait until we have an RTM SDK. I believe the arcade insertion is just doing it's thing propagating the arcade toolset changes here.
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.
We'll need a newer sdk to be able to take the new roslyn in #92503 (comment) but this pr is just to catch us up with normal arcade flow
I noticed we took the RC toolset update in 02bcb36. Among those other changes might be things needed here to update the toolset. |
The problem is the src/tests/Common/external/external.csproj project. It specifies The whole thing smells of giant hacks, but I bet updating to |
This - |
We don't have to do it in this PR, but I bet we can remove that RID. It looks to me like this dates back to 1.1 days where we had implementations in RID-specific packages. So in order to get NuGet to restore the right stuff to copy a RID that plugged into the graph was needed. b843687#diff-61c4029d873ebe0ce8a16d30a697127a7c96e11a1cc018936df1963aba0ef40bR12 |
And use the same condition as in main.
AFAIK, after the runtime tests are all migrated to the new source generated model (which should be completed soon), they will participate in NuGet restore and will get their dependencies directly, instead of via the external.csproj project. That project and setting a RID for restore will then go away. |
So installer rid resolution failures left (other than CI noise)? |
@lewing @ViktorHofer do we need to address those rid-related CI failures in this PR, or should I open a separate issue to get them fixed? |
Need to be addressed here. Those are real failures. |
Last commit ports over the below from main: Lines 2 to 8 in 9dfbb61
|
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.
CI is green and the two remaining feedback items were addressed by @elinor-fung and @lewing. Merging now.
Many thanks for resolving that. |
Arcade flow is stuck somewhere in release/8.0 this the result of running
darc update-dependencies --id 194643
manually.cc @ViktorHofer @mmitche