Skip to content

TimeoutFailsEvenWhenExitCodeIsIgnored intermittently fails on Mono #5506

Open

Description

Assert.Equal() Failure\nExpected: 143\nActual:   259


Stack trace
  at Microsoft.Build.UnitTests.Exec_Tests.TimeoutFailsEvenWhenExitCodeIsIgnored () [0x00050] in <e2bb78cae790436db9274dfd30d03cfc>:0 
  at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
  at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in <ba70b91736bd40cb990a357097dba9c3>:0 

I've seen this several times. No idea why the timed-out exit code is sometimes different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    MonoMono-specific issues. Also see https://github.com/mono/msbuildflaky-testTests that have failed but passed on rerun.testingtriaged

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions