File 4663-kernel-test-Sys-monitor-tweaking.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 4663-kernel-test-Sys-monitor-tweaking.patch of Package erlang

From 41486ea6358058ca2a533b9bf32d4dea3cd42ad0 Mon Sep 17 00:00:00 2001
From: Micael Karlberg <bmk@erlang.org>
Date: Thu, 27 Oct 2022 10:12:41 +0200
Subject: [PATCH 3/7] [kernel|test] Sys monitor tweaking

---
 lib/kernel/test/kernel_test_global_sys_monitor.erl | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/kernel/test/kernel_test_global_sys_monitor.erl b/lib/kernel/test/kernel_test_global_sys_monitor.erl
index f7a1e8501a..f3eb0f152f 100644
--- a/lib/kernel/test/kernel_test_global_sys_monitor.erl
+++ b/lib/kernel/test/kernel_test_global_sys_monitor.erl
@@ -237,7 +237,7 @@ call(Req, Timeout) when is_integer(Timeout) ->
 %% This peace of weirdness is because on some machines this call has
 %% hung (in a call during end_per_testcase, which had a 1 min timeout,
 %% or if that was the total time for the test case).
-%% But because it hung there, we don't really know what where it git stuck.
+%% But because it hung there, we don't really know where it got stuck.
 %% So, by making the call in a tmp process, that we supervise, we can
 %% keep control. Also, we change the default timeout from infinity to an
 %% actual time (16 seconds).
@@ -250,11 +250,11 @@ call(Req, Timeout1, Timeout2) ->
                             {?MODULE, Ref, Rep} ->
                                 exit(Rep)
                         after Timeout2 ->
-                                {error, timeout}
+                                exit({error, timeout})
                         end
                 catch
                     C:E:_ ->
-                        {error, {caught, C, E}}
+                        exit({error, {caught, C, E}})
                 end
         end,
     {Pid, Mon} = spawn_monitor(F),
-- 
2.35.3

Places

File 4663-kernel-test-Sys-monitor-tweaking.patch of Package erlang

Places