Skip to content
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

MonoTests.DebuggerTests.Crash test is flaky #11385

Closed
akoeplinger opened this issue Oct 25, 2018 · 2 comments

Comments

@akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Oct 25, 2018

Steps to Reproduce

  1. Run Mono.Debugger.Soft tests
  2. Observe flaky behavior of MonoTests.DebuggerTests.Crash

Current Behavior

https://jenkins.mono-project.com/job/test-mono-pull-request-amd64/20338/
https://jenkins.mono-project.com/job/test-mono-pull-request-amd64-cxx/1872/

Mono.Debugger.Soft.VMDisconnectedException : Exception of type 'Mono.Debugger.Soft.VMDisconnectedException' was thrown.

  at Mono.Debugger.Soft.Connection.disconnected_check () [0x00018] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Mono.Debugger.Soft/Connection.cs:1323 
  at Mono.Debugger.Soft.Connection.SendReceive (Mono.Debugger.Soft.Connection+CommandSet command_set, System.Int32 command, Mono.Debugger.Soft.Connection+PacketWriter packet) [0x00009] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Mono.Debugger.Soft/Connection.cs:1602 
  at Mono.Debugger.Soft.Connection.SendReceive (Mono.Debugger.Soft.Connection+CommandSet command_set, System.Int32 command) [0x00000] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Mono.Debugger.Soft/Connection.cs:1644 
  at Mono.Debugger.Soft.Connection.VM_Dispose () [0x00000] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Mono.Debugger.Soft/Connection.cs:1749 
  at Mono.Debugger.Soft.VirtualMachine.Detach () [0x00000] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachine.cs:139 
  at MonoTests.DebuggerTests.Crash () [0x0006c] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/Mono.Debugger.Soft/Test/dtest.cs:2480 
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in /mnt/jenkins/workspace/test-mono-pull-request-amd64-cxx/mcs/class/corlib/System.Reflection/MonoMethod.cs:324 

Expected Behavior

No crash.

On which platforms did you notice this

[ ] macOS
[ x ] Linux
[ ] Windows

Version Used: master


Disabled the test in a509e43.

@alexanderkyte

This comment has been minimized.

Copy link
Member

@alexanderkyte alexanderkyte commented Oct 26, 2018

The whole thing is wrapped in a try/ catch that catches that exception. Let me double check. There's probably a step in the Finally block that could fault.

@alexanderkyte

This comment has been minimized.

Copy link
Member

@alexanderkyte alexanderkyte commented Oct 26, 2018

It's always going to flake a very small portion of the time, we're relying on a closing socket having information sent over it before it closes. That flake results in the disconnection exception, which all the API consumers have to expect right now anyways. When the VM disconnected before the PR was merged, that would be thrown. About 19/20 times, it'll manage to send the event. It seems more unstable over localhost than on another machine.

What I'm saying is that this looks like an expected failure signal that should have been caught.

@alexanderkyte alexanderkyte self-assigned this Oct 26, 2018
thaystg added a commit to thaystg/mono that referenced this issue Jan 7, 2019
…ady have knowledge about the unreliability of the crash reporter and the test is not about it.

So if in 10 times at least one of them works for now it's good.
Fixes mono#11385
thaystg added a commit that referenced this issue Jan 9, 2019
* Changing the test behavior as discussed with Ludovic, because we already have knowledge about the unreliability of the crash reporter and the test is not about it.
So if in 10 times at least one of them works for now it's good.
Fixes #11385

* Removing extra message.

* Removing the crash log file after the test is finished.
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Apr 24, 2019
Bumps to mono/api-snapshot@ae01378
Bumps to mono/reference-assemblies@e5173a5
Bumps to mono/bockbuild@d30329d
Bumps to mono/boringssl@3d87996
Bumps to mono/corefx@72f7d76
Bumps to mono/corert@1b7d4a1
Bumps to mono/helix-binaries@7e893ea
Bumps to mono/illinker-test-assets@f21ff68
Bumps to mono/linker@13d864e
Bumps to mono/llvm@1aaaaa5 [mono]
Bumps to mono/llvm@2c2cffe [xamarin-android]
Bumps to mono/NUnitLite@0029561
Bumps to mono/roslyn-binaries@0bbc9b4
Bumps to mono/xunit-binaries@8f6e62e

	$ git diff --shortstat 886c4901..e66c7667      # mono
        3597 files changed, 350850 insertions(+), 91128 deletions(-)
	$ git diff --shortstat 349752c464c5fc93b32e7d45825f2890c85c8b7d..2c2cffedf01e0fe266b9aaad2c2563e05b750ff4
	 240 files changed, 18562 insertions(+), 6581 deletions(-)

Context: dotnet/coreclr#22046

Fixes: CVE 2018-8292 on macOS
Fixes: http://work.devdiv.io/737323
Fixes: dotnet/corefx#33965
Fixes: dotnet/standard#642
Fixes: mono/mono#6997
Fixes: mono/mono#7326
Fixes: mono/mono#7517
Fixes: mono/mono#7750
Fixes: mono/mono#7859
Fixes: mono/mono#8360
Fixes: mono/mono#8460
Fixes: mono/mono#8766
Fixes: mono/mono#8922
Fixes: mono/mono#9418
Fixes: mono/mono#9507
Fixes: mono/mono#9951
Fixes: mono/mono#10024
Fixes: mono/mono#10030
Fixes: mono/mono#10038
Fixes: mono/mono#10448
Fixes: mono/mono#10735
Fixes: mono/mono#10735
Fixes: mono/mono#10737
Fixes: mono/mono#10743
Fixes: mono/mono#10834
Fixes: mono/mono#10837
Fixes: mono/mono#10838
Fixes: mono/mono#10863
Fixes: mono/mono#10945
Fixes: mono/mono#11020
Fixes: mono/mono#11021
Fixes: mono/mono#11021
Fixes: mono/mono#11049
Fixes: mono/mono#11091
Fixes: mono/mono#11095
Fixes: mono/mono#11123
Fixes: mono/mono#11138
Fixes: mono/mono#11146
Fixes: mono/mono#11202
Fixes: mono/mono#11214
Fixes: mono/mono#11317
Fixes: mono/mono#11326
Fixes: mono/mono#11378
Fixes: mono/mono#11385
Fixes: mono/mono#11478
Fixes: mono/mono#11479
Fixes: mono/mono#11488
Fixes: mono/mono#11489
Fixes: mono/mono#11527
Fixes: mono/mono#11529
Fixes: mono/mono#11596
Fixes: mono/mono#11603
Fixes: mono/mono#11613
Fixes: mono/mono#11623
Fixes: mono/mono#11663
Fixes: mono/mono#11681
Fixes: mono/mono#11684
Fixes: mono/mono#11693
Fixes: mono/mono#11697
Fixes: mono/mono#11779
Fixes: mono/mono#11809
Fixes: mono/mono#11858
Fixes: mono/mono#11895
Fixes: mono/mono#11898
Fixes: mono/mono#11898
Fixes: mono/mono#11965
Fixes: mono/mono#12182
Fixes: mono/mono#12193
Fixes: mono/mono#12218
Fixes: mono/mono#12235
Fixes: mono/mono#12263
Fixes: mono/mono#12307
Fixes: mono/mono#12331
Fixes: mono/mono#12362
Fixes: mono/mono#12374
Fixes: mono/mono#12402
Fixes: mono/mono#12421
Fixes: mono/mono#12461
Fixes: mono/mono#12479
Fixes: mono/mono#12479
Fixes: mono/mono#12552
Fixes: mono/mono#12603
Fixes: mono/mono#12747
Fixes: mono/mono#12831
Fixes: mono/mono#12843
Fixes: mono/mono#12881
Fixes: mono/mono#13030
Fixes: mono/mono#13284
Fixes: mono/mono#13297
Fixes: mono/mono#13455
Fixes: mono/mono#13460
Fixes: mono/mono#13478
Fixes: mono/mono#13479
Fixes: mono/mono#13522
Fixes: mono/mono#13607
Fixes: mono/mono#13610
Fixes: mono/mono#13610
Fixes: mono/mono#13639
Fixes: mono/mono#13672
Fixes: mono/mono#13834
Fixes: mono/mono#13878
Fixes: mono/mono#6352
Fixes: mono/monodevelop#6898
Fixes: xamarin/maccore#1069
Fixes: xamarin/maccore#1407
Fixes: xamarin/maccore#604
Fixes: xamarin/xamarin-macios#4984
Fixes: xamarin/xamarin-macios#5289
Fixes: xamarin/xamarin-macios#5363
Fixes: xamarin/xamarin-macios#5381
Fixes: https://issuetracker.unity3d.com/issues/editor-crashes-with-g-logv-when-entering-play-mode-with-active-flowcanvas-script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.