summaryrefslogtreecommitdiff
path: root/thread_pthread.c
diff options
context:
space:
mode:
authorJean Boussier <jean.boussier@gmail.com>2022-07-13 18:49:27 +0200
committerJean Boussier <jean.boussier@gmail.com>2022-07-13 19:39:31 +0200
commit664c23db79dd0d500a834ef0ec8da443d95ddfd6 (patch)
tree520f941f548ebae183be735ece04cea5b4dd30d5 /thread_pthread.c
parent13d2ae6d4a83f059f46624f55f1e396cbf37c286 (diff)
downloadruby-664c23db79dd0d500a834ef0ec8da443d95ddfd6.tar.gz
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.
Diffstat (limited to 'thread_pthread.c')
-rw-r--r--thread_pthread.c9
1 files changed, 2 insertions, 7 deletions
diff --git a/thread_pthread.c b/thread_pthread.c
index 8597479765..86ad279d7c 100644
--- a/thread_pthread.c
+++ b/thread_pthread.c
@@ -449,13 +449,6 @@ thread_sched_to_waiting(struct rb_thread_sched *sched)
}
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)
{
rb_thread_t *next;
@@ -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 */