You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ok 287 - threadpool_cancel_work
not ok 288 - threadpool_multiple_event_loops
# timeout# Output from process `threadpool_multiple_event_loops`:# CEE5205S The signal SIGTERM was received.
threadpool_multiple_event_loops is calling getaddrinfo_concurrent as a separate job which cause it to also timeout.
getaddrinfo_concurrent is making a getaddrinfo system call which timeout at times. The reason is, system call is being made with locahost and OS might be trying to resolve it to an IP address.
64 r = uv_getaddrinfo(req->loop,
65 &req->handle,
66 getaddrinfo_cb,
67 "localhost",
changing localhost to 127.0.0.1 on both test cases and rerunning them fixed the issue however, calling localhost should be equivalent to calling 127.0.0.1. I will send a note to the marist IT team to discuss the issue first.
Activity
miladfarca commentedon Feb 20, 2019
threadpool_multiple_event_loopsis callinggetaddrinfo_concurrentas a separate job which cause it to also timeout.getaddrinfo_concurrentis making agetaddrinfosystem call which timeout at times. The reason is, system call is being made withlocahostand OS might be trying to resolve it to an IP address.changing
localhostto127.0.0.1on both test cases and rerunning them fixed the issue however, calling localhost should be equivalent to calling 127.0.0.1. I will send a note to the marist IT team to discuss the issue first.miladfarca commentedon Mar 19, 2019
Issue has been fixed on zOS.
mhdawson commentedon Mar 19, 2019
Recent runs have passed, closing