-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[Debugger] Crash test #12304
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
[Debugger] Crash test #12304
Conversation
This reverts commit 4d73377.
…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
|
@monojenkins build failed |
1 similar comment
|
@monojenkins build failed |
|
@monojenkins build failed |
|
It might be good to track this one down, the crash reporter is unreliable when dealing with random crashes, this one is a controlled one, so it should work. |
What do you suggest? What happens is that after the fork the parent process disappear(between the fork and this call mono_threads_summarize_execute) and only the child process continues. |
|
@monojenkins build failed |
1 similar comment
|
@monojenkins build failed |
|
@monojenkins build failed |
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