-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Update dependencies with darc #6714
Conversation
* Use Razor SDK version with workaround for dotnet#6500 * Remove package reference to Razor SDK in template
src/Components/src/Microsoft.AspNetCore.Components.Build/targets/RazorCompilation.targets
Outdated
Show resolved
Hide resolved
|
Sent email to figure out where that API went. |
Guessing you need a new runtime? dotnet/coreclr#21912 |
Progress:
|
@benaadams I ran update again to get the latest netcore.app. If the problem persists, then this will likely need to be sent to corefx/coreclr as a partner-blocking issues. |
Different one this time
|
Build and test: ANCM IIS Job
|
|
The test failures are consistent, not just flaky. @ajcvickers were there any recent changes in EF Core which might lead to this error?
|
Build failures this time due to dotnet/arcade#1677. The version of core-setup hasn't caught up with the version of corefx packages. |
Failure is unexpected assemblies
|
@benaadams - yes, this is the 'diamond dependency' problem I described in dotnet/arcade#1677. We don't have a good mechanism yet for telling Arcade that we can't take a version of corefx higher than what core-setup used. Until we have a fix for this, our dependency flow is going to take a lot of trial and error to get the right combination of versions. |
Waiting on dotnet/core-setup#4996. cc @dagood |
Test failures in Linux now.
@muratg @BrennanConroy @mikaelm12 - does this problem look familiar? |
Hmm, took a look at the build failure and I haven't seen that before |
@mikaelm12 can you investigate the signalr issue please? |
Yeah, will take a closer look |
Discussed with Nate. We think this is a possible regression in the new .Net Core runtime. Reaching out to the appropriate people. |
Might want to check corefx for issues on WaitForExit, see if there is anything related e.g. https://github.com/dotnet/corefx/issues/31713 |
@natemcmaster, agreed. |
@natemcmaster @benaadams this may help: you get this when you call |
Manually ran
darc update-dependencies -c '.NET Core 3 Dev'
.It missed: