From 7b2b44bce4bff85d9fd1bef09d294ddb889056e4 Mon Sep 17 00:00:00 2001 From: "Justin M. Keyes" Date: Sun, 19 Jun 2022 04:19:08 +0200 Subject: fix(ci): noisy logs, unreliable test #19019 Problem: 1. CI logs have too many (40+) logs mentioning SIGHUP: ``` WRN 2022-06-18T16:05:47.075 T3568.22499.0/c deadly_signal:177: got signal 1 (SIGHUP) WRN 2022-06-18T16:05:47.273 T3569.91095.0/c deadly_signal:177: got signal 1 (SIGHUP) WRN 2022-06-18T16:05:47.651 T3570.59545.0/c deadly_signal:177: got signal 1 (SIGHUP) ``` 2. TS parser test still sometimes fails on BSD CI. 3. remote_spec test fails too often. Solution: 1. Log deadly signals at INFO level. It hasn't been helpful in CI, and for local troubleshooting it's reasonable to adjust the loglevel as needed. 2. Adjust the TS parser test again. ref #18911 3. Skip the remote_spec test. The `--remote` feature was merged before it was fully formed and needs to be revisited. --- src/nvim/os/signal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/nvim/os/signal.c b/src/nvim/os/signal.c index cd591801ed..c6c43aac92 100644 --- a/src/nvim/os/signal.c +++ b/src/nvim/os/signal.c @@ -174,7 +174,7 @@ static void deadly_signal(int signum) set_vim_var_nr(VV_DYING, 1); v_dying = 1; - WLOG("got signal %d (%s)", signum, signal_name(signum)); + ILOG("got signal %d (%s)", signum, signal_name(signum)); snprintf((char *)IObuff, sizeof(IObuff), "Vim: Caught deadly signal '%s'\r\n", signal_name(signum)); -- cgit