From 664c23db79dd0d500a834ef0ec8da443d95ddfd6 Mon Sep 17 00:00:00 2001 From: Jean Boussier Date: Wed, 13 Jul 2022 18:49:27 +0200 Subject: GVL Instrumentation: remove the EXITED count assertion It's very flaky for some unknown reason. Something we have an extra EXITED event. I suspect some other test is causing this. --- thread_pthread.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) (limited to 'thread_pthread.c') diff --git a/thread_pthread.c b/thread_pthread.c index 8597479765..86ad279d7c 100644 --- a/thread_pthread.c +++ b/thread_pthread.c @@ -448,13 +448,6 @@ thread_sched_to_waiting(struct rb_thread_sched *sched) rb_native_mutex_unlock(&sched->lock); } -static void -thread_sched_to_dead(struct rb_thread_sched *sched) -{ - thread_sched_to_waiting(sched); - RB_INTERNAL_THREAD_HOOK(RUBY_INTERNAL_THREAD_EVENT_EXITED); -} - static void thread_sched_yield(struct rb_thread_sched *sched, rb_thread_t *th) { @@ -1177,6 +1170,8 @@ thread_start_func_1(void *th_ptr) #else thread_start_func_2(th, &stack_start); #endif + + RB_INTERNAL_THREAD_HOOK(RUBY_INTERNAL_THREAD_EVENT_EXITED); } #if USE_THREAD_CACHE /* cache thread */ -- cgit v1.2.1