search

bloomberg / ntf-core

Sockets, timers, resolvers, events, reactors, proactors, and thread pools for asynchronous network programming
Apache License 2.0
72 stars 23 forks source link

Failing tests in GitHub Actions #101

Closed 678098 closed 7 months ago

678098 commented 9 months ago

CI job: https://github.com/678098/ntf-core/actions/runs/6973299206/job/18977037069

Failed tests:

2023-11-23T18:47:34.7518843Z #10 723.7         Start  53: ntsu_resolverutil.t
2023-11-23T18:47:35.2027718Z #10 724.1  53/185 Test  #53: ntsu_resolverutil.t ..............Subprocess aborted***Exception:   0.39 sec
2023-11-23T18:48:07.2569847Z #10 756.1         Start  91: ntcs_controller.t
2023-11-23T18:58:07.3396223Z #10 1356.2  91/185 Test  #91: ntcs_controller.t ................***Timeout 600.05 sec
2023-11-23T18:58:58.7399024Z #10 1407.6         Start 129: ntcdns_database.t
2023-11-23T18:58:58.7399606Z #10 1407.7 129/185 Test #129: ntcdns_database.t ................Subprocess aborted***Exception:   0.08 sec
2023-11-23T18:58:58.7401169Z #10 1407.7         Start 131: ntcdns_resolver.t
2023-11-23T18:58:58.8466796Z #10 1407.7 131/185 Test #131: ntcdns_resolver.t ................Subprocess aborted***Exception:   0.08 sec
2023-11-23T18:58:58.9969108Z #10 1407.8         Start 134: ntcdns_utility.t
2023-11-23T18:58:58.9970542Z #10 1407.9 134/185 Test #134: ntcdns_utility.t .................Subprocess aborted***Exception:   0.08 sec
2023-11-23T19:00:29.8151829Z #10 1498.6         Start 162: ntcf_system.t
2023-11-23T19:10:29.7647993Z #10 2098.7 162/185 Test #162: ntcf_system.t ....................***Timeout 600.10 sec
2023-11-23T19:20:30.0281540Z #10 2698.8 180/185 Test #180: ntcu09.t .........................***Timeout 600.08 sec
2023-11-23T19:20:30.0282145Z #10 2698.8         Start 181: ntcu10.t
2023-11-23T19:30:29.9929705Z #10 3298.9 181/185 Test #181: ntcu10.t .........................***Timeout 600.02 sec
2023-11-23T19:30:29.9930461Z #10 3298.9         Start 182: ntcu11.t

We also have problems with recent ntf-core revisions in BlazingMQ broker, might be caused by same problems with resolver:

STDOUT: 16NOV2023_16:12:44.557 (140628113471040) INFO mqbnet_transportmanager.cpp:200 Client session is up [channel: '172.17.0.1:50352#0x7fe6540096a8']
STDOUT: 16NOV2023_16:12:44.564 (140627597579840) WARN mwcio_resolvingchannelfactory.cpp:258 Cannot resolve peerUri.  Resolution failed for 172.17.0.1:50352, Error: Invalid argument (EINVAL)
STDOUT: 16NOV2023_16:12:44.564 (140627597579840) INFO mqbnet_tcpsessionfactory.cpp:220 Channel 0x7fe654005460 with remote peer 172.17.0.1:50352 resolved to '' (took: 7.56 ms, 7555077 nanoseconds)
678098 commented 7 months ago

Tests are passing in CI now