Skip to content

Conversation

@mmitche
Copy link
Member

@mmitche mmitche commented Sep 21, 2021

No description provided.

@ghost
Copy link

ghost commented Sep 21, 2021

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

Issue Details

null

Author: mmitche
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

@mmitche mmitche changed the title Update to latest .NET 5 SDK [release/5.0] Update to latest .NET 5 SDK Sep 21, 2021
@mmitche
Copy link
Member Author

mmitche commented Sep 21, 2021

@danmoseley @jeffschwMSFT Required to unblock 5.0 builds.

@mmitche
Copy link
Member Author

mmitche commented Sep 21, 2021

@jeffschwMSFT Interesting test failures?

@jeffschwMSFT
Copy link
Member

It is 1 test failure that is failing consistently across these runs. @agocke / @mateoatr can y'all take a look at this 5.0 test failure?

  [3:55:32 PM] Running SatelliteAssembly_CultureSubdirectory...
  Test SatelliteAssembly_CultureSubdirectory failed: System.IO.FileNotFoundException: Could not load file or assembly 'AssemblyToLoad_Subdirectory.resources, Culture=fr-FR, PublicKeyToken=null'. The system cannot find the file specified.
  File name: 'AssemblyToLoad_Subdirectory.resources, Culture=fr-FR, PublicKeyToken=null'
     at System.Reflection.RuntimeAssembly.InternalLoad(ObjectHandleOnStack assemblyName, ObjectHandleOnStack requestingAssembly, StackCrawlMarkHandle stackMark, Boolean throwOnFileNotFound, ObjectHandleOnStack assemblyLoadContext, ObjectHandleOnStack retAssembly)
     at System.Reflection.RuntimeAssembly.InternalLoad(AssemblyName assemblyName, RuntimeAssembly requestingAssembly, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, AssemblyLoadContext assemblyLoadContext)
     at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyName(AssemblyName assemblyName)
     at BinderTracingTests.BinderTracingTest.SatelliteAssembly_CultureSubdirectory() in /Users/runner/work/1/s/src/tests/Loader/binding/tracing/BinderTracingTest.DefaultProbing.cs:line 160
     at BinderTracingTests.BinderTracingTest.RunSingleTest(MethodInfo method) in /Users/runner/work/1/s/src/tests/Loader/binding/tracing/BinderTracingTest.cs:line 171
  Expected: 100
  Actual: 101
  END EXECUTION - FAILED

@agocke
Copy link
Member

agocke commented Sep 22, 2021

Looking -- unfortunately it seems to have passed locally for me, so I'll need to investigate more

@mmitche
Copy link
Member Author

mmitche commented Sep 22, 2021

@agocke Should I merge this to unblock 5.0 or is this worrying enough to warrant holding off 5.0 for?

@mateoatr
Copy link
Contributor

I can repro and I'm looking why this started happening; not seeing anything obvious. Based on the csproj of the failing test, it looks like the assemblies are not being put in the expected location.

@mmitche
Copy link
Member Author

mmitche commented Sep 23, 2021

I can repro and I'm looking why this started happening; not seeing anything obvious. Based on the csproj of the failing test, it looks like the assemblies are not being put in the expected location.

So this looks like a test issue?

@jeffschwMSFT
Copy link
Member

Building on Matt's comment. If we feel this is a regression, what is the likely impact? Since this is the SDK to build the product, do we have this pattern and this is a guard against a later/subtle failure.

If we feel this has a low impact, we can disable and unblock this dependency flow and continue to investigate.

@agocke
Copy link
Member

agocke commented Sep 23, 2021

It also looks like it only happens in checked builds. We could probably disable the test for now while we investigate

@mmitche mmitche merged commit 6bfe74e into release/5.0 Sep 23, 2021
@jkotas jkotas deleted the mmitche-patch-1 branch September 24, 2021 04:32
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
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.

5 participants