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.
This commit is contained in:
Justin M. Keyes
2022-06-19 04:19:08 +02:00
committed by GitHub
parent 605631ac29
commit 7b2b44bce4
3 changed files with 4 additions and 4 deletions

View File

@@ -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));