Skip to content

z/os: threadpool_multiple_event_loops failure #1685

Closed

Description

@mhdawson

Seems to be failing since ~ 5 Feb

https://ci.nodejs.org/job/libuv-test-commit-zos/nodes=zos-s390x/1336/console

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.

Activity

  1. miladfarca commented on Feb 20, 2019

    @miladfarca
    Contributor
    getaddrinfo_concurrent
    threadpool_multiple_event_loops
    

    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.

  2. miladfarca commented on Mar 19, 2019

    @miladfarca
    Contributor

    Issue has been fixed on zOS.

  3. mhdawson commented on Mar 19, 2019

    @mhdawson
    MemberAuthor

    Recent runs have passed, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions