Remove net5 feeds

[ViktorHofer]

Fixes #41593
Depends on #43304

List of not flowing packages in the dotnet* feeds (in-complete):

• microsoft.private.intellisense
• optimization.*

cc @mmitche

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ViktorHofer]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

[danmoseley]

@ViktorHofer is this good to merge?

[ghost]

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

[ViktorHofer]

Nope... Need to work with @mmitche to get the non-flowing packages into the net6 feeds. Hasn't been a priority yet.

[ViktorHofer]

netstandard.library

@ericstj I don't think we want to continue using a netstandard 2.2 prerelease package. Should we downgrade our usage to the latest 2.1 released package?

[ericstj]

latest 2.1 released package

So long as that works with source build. @dseefeld

[dseefeld]

latest 2.1 released package

So long as that works with source build. @dseefeld Dan Seefeldt FTE

This should work for source-build. netstandard.library.ref 2.1.0 is built in source-build-reference-packages.

[ViktorHofer]

/azp run runtime

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

@dotnet/runtime-infrastructure who knows which component pushes the optimization data to the dotnet5 feed? We need to update that to the dotnet6 feed.

AFAIK microsoft.private.intellisense is published manually into our feed, hence we should manually publish the latest version into dotnet6 and update guidance.

[jkoritzinsky]

The internal dotnet-optimization repo produces the optimization data.

[ViktorHofer]

The internal dotnet-optimization repo produces the optimization data.

That pipeline has been failing since 9/29: https://dev.azure.com/dnceng/internal/_build?definitionId=237. Who ones that repo/infra?

[jkoritzinsky]

@agocke is working now on getting it back online.

[ViktorHofer]

@agocke is working now on getting it back online.

Should we track this pipeline in the CI Council dashboard? I assume it's @mmitche or @Anipik who did the default channel remapping from dotnet5 to dotnet6 back then? Who would the point of contact for that repo in general?

[agocke]

I can probably route as appropriate

[ViktorHofer]

I can probably route as appropriate

Thanks a lot @agocke. Do you have an ETA when the repo will be unblocked?

I will speak with @Chrisboh to include the optimization pipeline to the internal dashboard to track it going forward.

[agocke]

Hoping to get it done this week, just getting up to speed.

[ViktorHofer]

@agocke any update on the optimization internal repo?

[agocke]

I've made several fixes and have now run into a runtime crash that's blocking. Stack looks like:

coreclr.dll!ClrFree(void * p) Line 302 C++
coreclr.dll!operator delete[](void * p) Line 410 C++
coreclr.dll!MulticoreJitRecorder::WriteOutput(IStream * pStream) Line 557 C++
coreclr.dll!MulticoreJitRecorder::WriteOutput() Line 155 C++
coreclr.dll!MulticoreJitRecorder::StopProfile(bool) Line 951 C++
coreclr.dll!MulticoreJitRecorder::WriteMulticoreJitProfiler(_TP_CALLBACK_INSTANCE * pInstance, void * pvContext, _TP_TIMER * pTimer) Line 810 C++

I'm working to try to get a time-travel debugging repro, but I'm unfamiliar with the system so it may take a bit.

[agocke]

This is now blocked on #46778

[ViktorHofer]

@agocke looks like the related issue was fixed yesterday. I'm unsure how the optimization repo consumes new builds but I assume you are now unblocked?

[agocke]

I hope so, testing today

[agocke]

optimization should be unblocked and completing builds now

[ViktorHofer]

/azp run runtime-live-build

[azure-pipelines]

No pipelines are associated with this pull request.

[ViktorHofer]

/azp run runtime

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

I manually pushed the latest optimization packages to the dotnet6-transport feed as bits are still not flowing from the optimization repo.

[ViktorHofer]

/azp run runtime

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

/azp run dotnet-linker-tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

/azp run runtime-staging

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

/azp run runtime-dev-innerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ViktorHofer]

@dotnet/runtime-infrastructure this PR should be ready now. Would be great if you could approve. Thanks

We now know that the only dependencies that don't flow automatically are the optimization.* and the intellisense packages. Hopefully we can get the optimization ones hooked up onto dependency flow properly. The intellisense one afaik should go away anyway.

[ViktorHofer]

Failure is #32805