BinderTracingTest.ResolutionFlow.cmd timed out #37132

Activity

1. Dotnet-GitSync-Bot

   added

   area-Infrastructure-coreclrOnly use for closed issuesOnly use for closed issues

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on May 28, 2020
2. safern

   added

   blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

   on May 28, 2020
3. vitek-karas commented on May 29, 2020

   

   vitek-karas

   on May 29, 2020

   Member

   More actions

   /cc @elinor-fung @vitek-karas
4. am11 commented on Jun 1, 2020

   

   am11

   on Jun 1, 2020

   Member

   More actions

   Failed again in #37254.
   console log
5. safern commented on Jun 5, 2020

   

   safern

   on Jun 5, 2020

   MemberAuthor

   More actions

   Failed again in: https://helix.dot.net/api/2019-06-17/jobs/7f75d67d-78f2-485f-b900-2a1e13f121d1/workitems/PayloadGroup0/console
6. jashook commented on Jul 13, 2020

   

   jashook

   on Jul 13, 2020

   Contributor

   More actions

   Is the correct area assembly loader?
7. jashook

   removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jul 13, 2020
8. vitek-karas

   added

   area-AssemblyLoader-coreclronly use for closed issuesonly use for closed issues

   and removed

   area-Infrastructure-coreclrOnly use for closed issuesOnly use for closed issues

   on Jul 13, 2020
10. vitek-karas commented on Jul 13, 2020

    

    vitek-karas

    on Jul 13, 2020

    Member

    More actions

    Can we determine when was the last time we saw this failure? @elinor-fung added some fixes relatively recently to the binder tracing tests - maybe it has already been fixed.
11. AntonLapounov commented on Jul 17, 2020

    

    AntonLapounov

    on Jul 17, 2020

    Contributor

    More actions

    This test failed in my PR (CoreCLR Pri0 Runtime Tests Run Windows_NT arm checked).
    https://helix.dot.net/api/2019-06-17/jobs/97e4a4cc-c6f6-4393-87cd-50b9aabe3ca2/workitems/PayloadGroup0/console

        Loader\binding\tracing\BinderTracingTest.ResolutionFlow\BinderTracingTest.ResolutionFlow.cmd [FAIL]
          Return code:      1
          Raw output file:      D:\h\w\B4F40A09\w\B07D094D\e\Loader\binding\Reports\Loader.binding\tracing\BinderTracingTest.ResolutionFlow\BinderTracingTest.ResolutionFlow.output.txt
          Raw output:
          BEGIN EXECUTION
           "D:\h\w\B4F40A09\p\corerun.exe" BinderTracingTest.ResolutionFlow.dll 
          [1:05:59 PM] Launching process for AppDomainAssemblyResolveEvent_Exception...
          [1:05:59 PM] Running AppDomainAssemblyResolveEvent_Exception...
          
          [1:06:00 PM] Launching process for LoadFromAssemblyPath_FoundInAppPath...
          [1:06:00 PM] Running LoadFromAssemblyPath_FoundInAppPath...
          
          [1:06:01 PM] Launching process for LoadFromAssemblyPath_FoundInLoadContext_DifferentMvid...
          [1:06:02 PM] Running LoadFromAssemblyPath_FoundInLoadContext_DifferentMvid...
          
          [1:06:02 PM] Launching process for LoadFromAssemblyPath_FoundInAppPath_IncompatibleVersion...
          [1:06:03 PM] Running LoadFromAssemblyPath_FoundInAppPath_IncompatibleVersion...
          
          [1:06:03 PM] Running AssemblyLoadContextResolving_ReturnNull...
          Test AssemblyLoadContextResolving_ReturnNull failed: System.AggregateException: One or more errors occurred. (An error occurred when writing to a listener.)
           ---> System.Diagnostics.Tracing.EventSourceException: An error occurred when writing to a listener.
           ---> System.ArgumentNullException: Value cannot be null. (Parameter 'source')
             at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) in /_/src/libraries/System.Linq/src/System/Linq/ThrowHelper.cs:line 12
             at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate) in /_/src/libraries/System.Linq/src/System/Linq/AnyAll.cs:line 51
             at BinderTracingTests.BinderEventListener.IsLoadToTrack(String name) in /Users/runner/work/1/s/src/tests/Loader/binding/tracing/BinderEventListener.cs:line 361
             at BinderTracingTests.BinderEventListener.OnEventWritten(EventWrittenEventArgs data) in /Users/runner/work/1/s/src/tests/Loader/binding/tracing/BinderEventListener.cs:line 343
             at System.Diagnostics.Tracing.EventSource.DispatchToAllListeners(Int32 eventId, EventWrittenEventArgs eventCallbackArgs)
             --- End of inner exception stack trace ---
             at System.Diagnostics.Tracing.EventSource.DispatchToAllListeners(Int32 eventId, EventWrittenEventArgs eventCallbackArgs)
             at System.Diagnostics.Tracing.EventSource.WriteToAllListeners(Int32 eventId, UInt32* osThreadId, DateTime* timeStamp, Guid* activityID, Guid* childActivityID, Object[] args)
             at System.Diagnostics.Tracing.EventPipeEventDispatcher.DispatchEventsToEventListeners()
             at System.Threading.Tasks.Task.InnerInvoke()
             at System.Threading.Tasks.Task.<>c.<.cctor>b__277_0(Object obj)
             at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
          --- End of stack trace from previous location ---
             at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
             at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
             --- End of inner exception stack trace ---
             at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
             at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
             at System.Threading.Tasks.Task.Wait()
             at System.Diagnostics.Tracing.EventPipeEventDispatcher.StopDispatchTask()
             at System.Diagnostics.Tracing.EventPipeEventDispatcher.CommitDispatchConfiguration()
             at System.Diagnostics.Tracing.EventPipeEventDispatcher.RemoveEventListener(EventListener listener)
             at System.Diagnostics.Tracing.EventListener.RemoveReferencesToListenerInEventSources(EventListener listenerToRemove)
             at System.Diagnostics.Tracing.EventListener.Dispose()
             at BinderTracingTests.BinderTracingTest.RunSingleTest(MethodInfo method) in /Users/runner/work/1/s/src/tests/Loader/binding/tracing/BinderTracingTest.cs:line 173
          Expected: 100
          Actual: 101
          END EXECUTION - FAILED
          FAILED
    
12. vitek-karas commented on Jul 20, 2020

    

    vitek-karas

    on Jul 20, 2020

    Member

    More actions

    The second failure makes no sense to me:
    It's failing because the this.loadsToTrack is null here:

    runtime/src/tests/Loader/binding/tracing/BinderEventListener.cs

    Line 361 in 9a5ef96

    return this.loadsToTrack.Any(n => n.Equals(name, StringComparison.InvariantCultureIgnoreCase));

    But that variable is initialized to the .ctor argument in the .ctor here:

    runtime/src/tests/Loader/binding/tracing/BinderEventListener.cs

    Line 170 in 9a5ef96

    this.loadsToTrack = loadsToTrack;

    This is the only .ctor the class has. The .ctor is called from just one place here:

    runtime/src/tests/Loader/binding/tracing/BinderTracingTest.cs

    Line 169 in 9a5ef96

    using (var listener = new BinderEventListener(loadsToTrack))

    That place passes the argument as a value returned by either new string[] or Union call, neither should ever return null. It's also not an initialization timing issue, since the failure occurs during Dispose which is called only after the initialization is fully done (via a using statement).
13. jkotas commented on Sep 3, 2020

    

    jkotas

    on Sep 3, 2020

    Member

    More actions

    Failed in #41757
14. agocke

    added this to the Future milestone on Sep 21, 2020
15. jaredpar commented on Oct 6, 2020

    

    jaredpar

    on Oct 6, 2020

    Member

    More actions

    Note this failed again today. I've made this a live issue so failures will be tracked in the main body.
16. janvorli commented on Nov 27, 2020

    

    janvorli

    on Nov 27, 2020

    Member

    More actions

    I keep hitting the timeout locally on my macOS device consistently.
17. hoyosjs commented on Dec 3, 2020

    

    hoyosjs

    on Dec 3, 2020

    Member

    More actions

    @sywhang and I took a look at this. It is a product issue that can cause deadlocks. It can hit any test that uses tracing (like BinderTracingTest.Basic and BinderTracingTest.ResolutionFlow do).
18. ghost closed this as completedin #45570on Dec 4, 2020
19. ghost locked as resolved and limited conversation to collaborators on May 12, 2021