Re-enable templating tests in 3.0

[JunTaoLuo]

I turned off the template tests to unblock #12977. We need to make sure these tests are turned back on ASAP.

[Pilchie]

Adding @mkArtakMSFT here. Is this something someone from your team could look at?

[mkArtakMSFT]

@javiercn I know you've done a lot of changes in this area during our infrastructure effort, which is still going on. I'm wondering whether this is already fixed. If not, can you please re-enable these?

[javiercn]

I added a change to capture binlogs on the CI. It seems that you folks broke this as part of the infrastructure update.

[javiercn]

@mkArtakMSFT Please reassign, as this is build infrastructure specific.

[mkArtakMSFT]

@JunTaoLuo and I talked and he will follow up with @javiercn to understand what exactly is broken regarding change to capture binlogs on the CI. As for this issue, we just need to re-enable the disabled tests, @javiercn. I suggest we track these two changes separately, so feel free to file a new issue, if necessary, for the investigation.

[JunTaoLuo]

This has to do with the SDK that's being used. To build our 5.0 projects, we have to apply some workarounds until the SDK has ingested a version of our AspNetCore shared framework. That was done in dotnet/installer#4391 so we should be able update the SDK and resolve this issue. If a new SDK is not available, I can point you to the workaround we have in place which needs to be copied locally to the temporary test project. But as @mkArtakMSFT mentioned, this should not be related to the original issue.

[javiercn]

How long will it take for the new SDK to be available? At that point that would solve the issue, won’t it? How involved is the workaround?

[javiercn]

@JunTaoLuo Just to clarify things.

• What's broken is that the E2E template tests got disabled in the PR above.
• I made a change to enable capturing binlogs and allow troubleshooting what was going on. (Its merged in 3.1 and I cherry-picked into a branch from master in a separate PR that tried to re-enable the tests to troubleshoot it)
• As a result of that I took the screenshot above from one of the failing binlogs.

There is no issue with the binlogs. Everything works just fine, but the template tests and still broken and disabled in master, which is what we are trying to solve. The questions that I have are:

• How do we apply the workaround you mention in [master] Update dependencies from aspnet/AspNetCore installer#4391?
• Will this issue go away once we ingest a new SDK?
  • If that's the case, how long will it take?

I'm happy if the outcome from this is we can just wait a few days after we ingest a new SDK and then re-enable the tests. Could we tie the two things together? (Ingest the SDK and reenable the E2E tests on the same PR).

Otherwise, can you help in applying the workaround?

[JunTaoLuo]

I just checked the latest SDK and it has already ingested a 5.0 AspNetCore shared framework so updating the SDK to 5.0.100-alpha1-014713 should fix the issue you're seeing in the template tests. And yes, you should update the SDK when re-enabling the template tests.