Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More struct thread null #9763

Merged
merged 4 commits into from
Oct 12, 2021
Merged

More struct thread null #9763

merged 4 commits into from
Oct 12, 2021

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Oct 7, 2021

No description provided.

@ton31337
Copy link
Member Author

ton31337 commented Oct 7, 2021

@frrbot rereview

@LabN-CI
Copy link
Collaborator

LabN-CI commented Oct 7, 2021 •
edited
Loading

Outdated results 💚

Basic BGPD CI results: SUCCESS, 0 tests failed

_ _
Result SUCCESS git merge/9763 aa06c8e
Date 10/07/2021
Start 06:01:18
Finish 06:27:31
Run-Time 26:13
Total 1813
Pass 1813
Fail 0
Valgrind-Errors 0
Valgrind-Loss 0
Details vncregress-2021-10-07-06:01:18.txt
Log autoscript-2021-10-07-06:02:25.log.bz2
Memory 485 496 423

For details, please contact louberger

@idryzhov
Copy link
Contributor

idryzhov commented Oct 7, 2021

Some of these are actual bugs like #9758.
We should never pass a pointer to a local variable as a thread reference to thread_add_*.
I am going to submit a PR to fix all such bugs.

@ton31337 ton31337 force-pushed the fix/more_thread_null branch 3 times, most recently from 3d06538 to 22e5a7a Compare October 7, 2021 11:37
@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-634/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 7: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 7: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests Ubuntu 18.04 amd64 part 7: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 7: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests debian 10 amd64 part 6: Failed (click for details) Topotests debian 10 amd64 part 6: No useful log found
Topotests debian 10 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-634/test

Topology Tests failed for Topotests debian 10 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 09:50:50.851 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 09:50:51.536 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 09:50:52.734 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 09:50:52.734 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 09:50:52.734 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 09:50:52.735 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 09:50:52.735 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 09:50:52.792 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 09:50:52.792 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 09:50:52.792 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 09:50:52.792 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 09:50:52.792 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 09:50:52.792 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 09:50:52.793 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 09:50:52.793 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 09:50:52.793 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 09:50:52.793 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 09:50:52.793 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 09:50:52.799 LDP: waiting for children to terminate\n2021/10/07 09:50:52.799 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-634/artifact/TOPO7DEB10AMD64/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-634/test

Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 09:52:28.964 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 09:52:29.796 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 09:52:30.848 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 09:52:30.848 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 09:52:30.848 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 09:52:30.848 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 09:52:30.849 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 09:52:31.348 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 09:52:31.348 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 09:52:31.348 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 09:52:31.348 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 09:52:31.348 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 09:52:31.349 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 09:52:31.357 LDP: waiting for children to terminate\n2021/10/07 09:52:31.357 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-634/artifact/TOPO7U18I386/ErrorLog/log_topotests.txt

Successful on other platforms/tests
  • Topotests Ubuntu 18.04 i386 part 3
  • Topotests Ubuntu 18.04 i386 part 8
  • Addresssanitizer topotests part 0
  • Topotests Ubuntu 18.04 amd64 part 2
  • Topotests debian 10 amd64 part 8
  • Topotests debian 10 amd64 part 4
  • Topotests debian 10 amd64 part 9
  • Topotests Ubuntu 18.04 arm8 part 4
  • Addresssanitizer topotests part 4
  • Topotests Ubuntu 18.04 arm8 part 9
  • Topotests debian 10 amd64 part 3
  • Debian 9 deb pkg check
  • IPv6 protocols on Ubuntu 18.04
  • Addresssanitizer topotests part 1
  • Topotests Ubuntu 18.04 i386 part 4
  • Topotests Ubuntu 18.04 arm8 part 3
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests debian 10 amd64 part 2
  • IPv4 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 arm8 part 0
  • Static analyzer (clang)
  • Topotests Ubuntu 18.04 arm8 part 2
  • Topotests debian 10 amd64 part 0
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 9
  • Addresssanitizer topotests part 7
  • Ubuntu 20.04 deb pkg check
  • Topotests Ubuntu 18.04 i386 part 1
  • Topotests Ubuntu 18.04 amd64 part 5
  • Debian 10 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 5
  • IPv4 ldp protocol on Ubuntu 18.04
  • Addresssanitizer topotests part 5
  • Topotests debian 10 amd64 part 1
  • Topotests Ubuntu 18.04 arm8 part 1
  • Topotests Ubuntu 18.04 amd64 part 0
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 i386 part 0
  • Addresssanitizer topotests part 3
  • Addresssanitizer topotests part 2
  • Fedora 29 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 4
  • CentOS 7 rpm pkg check
  • Topotests Ubuntu 18.04 i386 part 9
  • Topotests Ubuntu 18.04 amd64 part 3
  • Topotests Ubuntu 18.04 i386 part 2
  • Topotests debian 10 amd64 part 5
  • Addresssanitizer topotests part 8
  • Topotests Ubuntu 18.04 arm8 part 8
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 amd64 part 1
  • Ubuntu 18.04 deb pkg check

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Failed

Debian 9 amd64 build: Failed (click for details)

Make failed for Debian 9 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/config.status/config.status
Debian 9 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/config.log/config.log.gz

Ubuntu 20.04 amd64 build: Failed (click for details) Ubuntu 20.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/config.status/config.status

Make failed for Ubuntu 20.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 20.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/config.log/config.log.gz

Ubuntu 18.04 ppc64le build: Failed (click for details)

Make failed for Ubuntu 18.04 ppc64le build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 ppc64le build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/config.status/config.status
Ubuntu 18.04 ppc64le build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/config.log/config.log.gz

CentOS 8 amd64 build: Failed (click for details) CentOS 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/config.status/config.status

Make failed for CentOS 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

CentOS 8 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/config.log/config.log.gz

FreeBSD 12 amd64 build: Failed (click for details)

Make failed for FreeBSD 12 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/usr/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]

FreeBSD 12 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/config.status/config.status
FreeBSD 12 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/config.log/config.log.gz

Ubuntu 18.04 arm7 build: Failed (click for details)

Make failed for Ubuntu 18.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 arm7 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/config.log/config.log.gz
Ubuntu 18.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/config.status/config.status

Fedora 29 amd64 build: Failed (click for details)

Make failed for Fedora 29 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Fedora 29 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/config.status/config.status
Fedora 29 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/config.log/config.log.gz

Ubuntu 18.04 arm8 build: Failed (click for details) Ubuntu 18.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/config.status/config.status Ubuntu 18.04 arm8 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/config.log/config.log.gz

Make failed for Ubuntu 18.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
FreeBSD 11 amd64 build: Failed (click for details)

Make failed for FreeBSD 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/usr/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]
lib/resolver.c: In function 'resolver_cb_socket_writable':
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable 't_ptr' [-Werror=unused-variable]

FreeBSD 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/config.status/config.status
FreeBSD 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/config.log/config.log.gz

Debian 10 amd64 build: Failed (click for details) Debian 10 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/config.log/config.log.gz

Make failed for Debian 10 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 10 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/config.status/config.status

Ubuntu 16.04 arm7 build: Failed (click for details) Ubuntu 16.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/config.status/config.status Ubuntu 16.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/config.log/config.log.gz

Make failed for Ubuntu 16.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
Debian 11 amd64 build: Failed (click for details) Debian 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/config.status/config.status

Make failed for Debian 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/config.log/config.log.gz

Ubuntu 16.04 i386 build: Failed (click for details)

Make failed for Ubuntu 16.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/config.status/config.status
Ubuntu 16.04 i386 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/config.log/config.log.gz

Ubuntu 16.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 16.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/config.status/config.status
Ubuntu 16.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/config.log/config.log.gz

Ubuntu 18.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 18.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/config.status/config.status
Ubuntu 18.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/config.log/config.log.gz

Ubuntu 16.04 arm8 build: Failed (click for details)

Make failed for Ubuntu 16.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 arm8 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/config.log/config.log.gz
Ubuntu 16.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/config.status/config.status

Ubuntu 18.04 i386 build: Failed (click for details) Ubuntu 18.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/config.log/config.log.gz Ubuntu 18.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/config.status/config.status

Make failed for Ubuntu 18.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
OpenBSD 6 amd64 build: Failed (click for details)

Make failed for OpenBSD 6 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c:60:1: error: version control conflict marker in file
<<<<<<< HEAD
^
lib/resolver.c:81:1: error: version control conflict marker in file
<<<<<<< HEAD
^
2 errors generated.

OpenBSD 6 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/config.status/config.status
OpenBSD 6 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/config.log/config.log.gz

CentOS 7 amd64 build: Failed (click for details)

Make failed for CentOS 7 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory `/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: expected expression before '<<' token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before '==' token
 =======
 ^
lib/resolver.c:55:18: warning: unused variable 't_ptr' [-Wunused-variable]

CentOS 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/config.status/config.status
CentOS 7 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/config.log/config.log.gz

NetBSD 8 amd64 build: Failed (click for details) NetBSD 8 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/config.log/config.log.gz

Make failed for NetBSD 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: expected expression before '<<' token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before '==' token
 =======
 ^
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]

NetBSD 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/config.status/config.status

Warnings Generated during build:

Checkout code: Successful with additional warnings
Debian 9 amd64 build: Failed (click for details)

Make failed for Debian 9 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/config.status/config.status
Debian 9 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI021BUILD/config.log/config.log.gz

Ubuntu 20.04 amd64 build: Failed (click for details) Ubuntu 20.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/config.status/config.status

Make failed for Ubuntu 20.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 20.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U2004AMD64BUILD/config.log/config.log.gz

Ubuntu 18.04 ppc64le build: Failed (click for details)

Make failed for Ubuntu 18.04 ppc64le build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 ppc64le build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/config.status/config.status
Ubuntu 18.04 ppc64le build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804PPC64LEBUILD/config.log/config.log.gz

CentOS 8 amd64 build: Failed (click for details) CentOS 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/config.status/config.status

Make failed for CentOS 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

CentOS 8 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CENTOS8BUILD/config.log/config.log.gz

FreeBSD 12 amd64 build: Failed (click for details)

Make failed for FreeBSD 12 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/usr/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]

FreeBSD 12 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/config.status/config.status
FreeBSD 12 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/FBSD12AMD64/config.log/config.log.gz

Ubuntu 18.04 arm7 build: Failed (click for details)

Make failed for Ubuntu 18.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 arm7 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/config.log/config.log.gz
Ubuntu 18.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM7BUILD/config.status/config.status

Fedora 29 amd64 build: Failed (click for details)

Make failed for Fedora 29 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Fedora 29 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/config.status/config.status
Fedora 29 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/F29BUILD/config.log/config.log.gz

Ubuntu 18.04 arm8 build: Failed (click for details) Ubuntu 18.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/config.status/config.status Ubuntu 18.04 arm8 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/config.log/config.log.gz

Make failed for Ubuntu 18.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
FreeBSD 11 amd64 build: Failed (click for details)

Make failed for FreeBSD 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/usr/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]
lib/resolver.c: In function 'resolver_cb_socket_writable':
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable 't_ptr' [-Werror=unused-variable]

FreeBSD 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/config.status/config.status
FreeBSD 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI009BUILD/config.log/config.log.gz

Debian 10 amd64 build: Failed (click for details) Debian 10 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/config.log/config.log.gz

Make failed for Debian 10 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 10 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB10BUILD/config.status/config.status

Ubuntu 16.04 arm7 build: Failed (click for details) Ubuntu 16.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/config.status/config.status Ubuntu 16.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/config.log/config.log.gz

Make failed for Ubuntu 16.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI101BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
Debian 11 amd64 build: Failed (click for details) Debian 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/config.status/config.status

Make failed for Debian 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
lib/resolver.c:62:1: error: version control conflict marker in file
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:81:1: error: version control conflict marker in file
lib/resolver.c:83:1: error: version control conflict marker in file
lib/resolver.c:76:18: error: unused variable t_ptr [-Werror=unused-variable]

Debian 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/DEB11AMD64/config.log/config.log.gz

Ubuntu 16.04 i386 build: Failed (click for details)

Make failed for Ubuntu 16.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/config.status/config.status
Ubuntu 16.04 i386 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1604I386/config.log/config.log.gz

Ubuntu 16.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 16.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/config.status/config.status
Ubuntu 16.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI014BUILD/config.log/config.log.gz

Ubuntu 18.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 18.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/config.status/config.status
Ubuntu 18.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U1804AMD64/config.log/config.log.gz

Ubuntu 16.04 arm8 build: Failed (click for details)

Make failed for Ubuntu 16.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: expected expression before << token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before == token
 =======
 ^
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]

Ubuntu 16.04 arm8 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/config.log/config.log.gz
Ubuntu 16.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U16ARM8BUILD/config.status/config.status

Ubuntu 18.04 i386 build: Failed (click for details) Ubuntu 18.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/config.log/config.log.gz Ubuntu 18.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/config.status/config.status

Make failed for Ubuntu 18.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/U18I386BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function resolver_cb_socket_readable:
lib/resolver.c:60:1: error: version control conflict marker in file
 <<<<<<< HEAD
 ^~~~~~~
lib/resolver.c:62:1: error: version control conflict marker in file
 =======
 ^~~~~~~
lib/resolver.c:55:18: error: unused variable t_ptr [-Werror=unused-variable]
OpenBSD 6 amd64 build: Failed (click for details)

Make failed for OpenBSD 6 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c:60:1: error: version control conflict marker in file
<<<<<<< HEAD
^
lib/resolver.c:81:1: error: version control conflict marker in file
<<<<<<< HEAD
^
2 errors generated.

OpenBSD 6 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/config.status/config.status
OpenBSD 6 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI011BUILD/config.log/config.log.gz

CentOS 7 amd64 build: Failed (click for details)

Make failed for CentOS 7 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory `/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: expected expression before '<<' token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before '==' token
 =======
 ^
lib/resolver.c:55:18: warning: unused variable 't_ptr' [-Wunused-variable]

CentOS 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/config.status/config.status
CentOS 7 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI005BUILD/config.log/config.log.gz

NetBSD 8 amd64 build: Failed (click for details) NetBSD 8 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/config.log/config.log.gz

Make failed for NetBSD 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/ErrorLog/log_make.txt)

gmake[1]: Entering directory '/home/ci/cibuild.635/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_readable':
lib/resolver.c:60:1: error: expected expression before '<<' token
 <<<<<<< HEAD
 ^
lib/resolver.c:62:1: error: expected expression before '==' token
 =======
 ^
lib/resolver.c:55:18: error: unused variable 't_ptr' [-Werror=unused-variable]

NetBSD 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-635/artifact/CI012BUILD/config.status/config.status

Report for resolver.c | 32 issues
===============================================
< WARNING: suspect code indent for conditional statements (8, 0)
< #59: FILE: /tmp/f1-14058/resolver.c:59:
< ERROR: spaces required around that '<' (ctx:OxW)
< #60: FILE: /tmp/f1-14058/resolver.c:60:
< ERROR: spaces required around that '==' (ctx:ExO)
< #62: FILE: /tmp/f1-14058/resolver.c:62:
< ERROR: spaces required around that '==' (ctx:OxO)
< #62: FILE: /tmp/f1-14058/resolver.c:62:
< ERROR: spaces required around that '==' (ctx:OxO)
< #62: FILE: /tmp/f1-14058/resolver.c:62:
< ERROR: spaces required around that '=' (ctx:OxE)
< #62: FILE: /tmp/f1-14058/resolver.c:62:
< ERROR: spaces required around that '>' (ctx:OxW)
< #63: FILE: /tmp/f1-14058/resolver.c:63:
< ERROR: spaces required around that ':' (ctx:VxW)
< #63: FILE: /tmp/f1-14058/resolver.c:63:
< WARNING: suspect code indent for conditional statements (8, 0)
< #80: FILE: /tmp/f1-14058/resolver.c:80:
< ERROR: spaces required around that '<' (ctx:OxW)
< #81: FILE: /tmp/f1-14058/resolver.c:81:
< ERROR: spaces required around that '==' (ctx:ExO)
< #83: FILE: /tmp/f1-14058/resolver.c:83:
< ERROR: spaces required around that '==' (ctx:OxO)
< #83: FILE: /tmp/f1-14058/resolver.c:83:
< ERROR: spaces required around that '==' (ctx:OxO)
< #83: FILE: /tmp/f1-14058/resolver.c:83:
< ERROR: spaces required around that '=' (ctx:OxE)
< #83: FILE: /tmp/f1-14058/resolver.c:83:
< ERROR: spaces required around that '>' (ctx:OxW)
< #84: FILE: /tmp/f1-14058/resolver.c:84:
< ERROR: spaces required around that ':' (ctx:VxW)
< #84: FILE: /tmp/f1-14058/resolver.c:84:

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Failed

Ubuntu 18.04 arm8 build: Failed (click for details) Ubuntu 18.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM8BUILD/config.status/config.status Ubuntu 18.04 arm8 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM8BUILD/config.log/config.log.gz

Make failed for Ubuntu 18.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input
Debian 9 amd64 build: Failed (click for details)

Make failed for Debian 9 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI021BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Debian 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI021BUILD/config.status/config.status
Debian 9 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI021BUILD/config.log/config.log.gz

Ubuntu 20.04 amd64 build: Failed (click for details) Ubuntu 20.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U2004AMD64BUILD/config.status/config.status

Make failed for Ubuntu 20.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U2004AMD64BUILD/ErrorLog/log_make.txt)

make  all-am
make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
make[1]: *** [Makefile:15495: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?

Ubuntu 20.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U2004AMD64BUILD/config.log/config.log.gz

CentOS 8 amd64 build: Failed (click for details) CentOS 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CENTOS8BUILD/config.status/config.status

Make failed for CentOS 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CENTOS8BUILD/ErrorLog/log_make.txt)

make  all-am
make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
 }
 
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
make[1]: *** [Makefile:15494: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function resolver_cb_socket_writable:

CentOS 8 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CENTOS8BUILD/config.log/config.log.gz

Ubuntu 18.04 ppc64le build: Failed (click for details)

Make failed for Ubuntu 18.04 ppc64le build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804PPC64LEBUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 18.04 ppc64le build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804PPC64LEBUILD/config.status/config.status
Ubuntu 18.04 ppc64le build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804PPC64LEBUILD/config.log/config.log.gz

Debian 10 amd64 build: Failed (click for details) Debian 10 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB10BUILD/config.log/config.log.gz

Make failed for Debian 10 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB10BUILD/ErrorLog/log_make.txt)

make  all-am
make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
 }
 
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
make[1]: *** [Makefile:15495: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function resolver_cb_socket_writable:

Debian 10 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB10BUILD/config.status/config.status

Fedora 29 amd64 build: Failed (click for details)

Make failed for Fedora 29 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/F29BUILD/ErrorLog/log_make.txt)

make  all-am
make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
 }
 
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
make[1]: *** [Makefile:15494: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function resolver_cb_socket_writable:

Fedora 29 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/F29BUILD/config.status/config.status
Fedora 29 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/F29BUILD/config.log/config.log.gz

Ubuntu 18.04 arm7 build: Failed (click for details)

Make failed for Ubuntu 18.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM7BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 18.04 arm7 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM7BUILD/config.log/config.log.gz
Ubuntu 18.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18ARM7BUILD/config.status/config.status

FreeBSD 11 amd64 build: Failed (click for details)

Make failed for FreeBSD 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI009BUILD/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/usr/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
gmake[1]: *** [Makefile:15506: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function 'resolver_cb_socket_writable':
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
lib/resolver.c:79:3: error: 'thread_add_write' undeclared (first use in this function); did you mean 'thread_cmd_init'?

FreeBSD 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI009BUILD/config.status/config.status
FreeBSD 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI009BUILD/config.log/config.log.gz

Ubuntu 16.04 arm7 build: Failed (click for details) Ubuntu 16.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI101BUILD/config.status/config.status Ubuntu 16.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI101BUILD/config.log/config.log.gz

Make failed for Ubuntu 16.04 arm7 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI101BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input
Ubuntu 16.04 i386 build: Failed (click for details)

Make failed for Ubuntu 16.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1604I386/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1604I386/config.status/config.status
Ubuntu 16.04 i386 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1604I386/config.log/config.log.gz

Ubuntu 18.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 18.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804AMD64/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804AMD64/config.status/config.status
Ubuntu 18.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U1804AMD64/config.log/config.log.gz

Debian 11 amd64 build: Failed (click for details) Debian 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB11AMD64/config.status/config.status

Make failed for Debian 11 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB11AMD64/ErrorLog/log_make.txt)

make  all-am
make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
make[1]: *** [Makefile:15507: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287: error: unterminated argument list invoking macro "thread_add_write"
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?

Debian 11 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/DEB11AMD64/config.log/config.log.gz

FreeBSD 12 amd64 build: Failed (click for details)

Make failed for FreeBSD 12 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/FBSD12AMD64/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/usr/home/ci/cibuild.636/frr-source'
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
gmake[1]: *** [Makefile:15494: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function 'resolver_cb_socket_writable':

FreeBSD 12 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/FBSD12AMD64/config.status/config.status
FreeBSD 12 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/FBSD12AMD64/config.log/config.log.gz

Ubuntu 16.04 amd64 build: Failed (click for details)

Make failed for Ubuntu 16.04 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI014BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 16.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI014BUILD/config.status/config.status
Ubuntu 16.04 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI014BUILD/config.log/config.log.gz

Ubuntu 16.04 arm8 build: Failed (click for details)

Make failed for Ubuntu 16.04 arm8 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U16ARM8BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

Ubuntu 16.04 arm8 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U16ARM8BUILD/config.log/config.log.gz
Ubuntu 16.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U16ARM8BUILD/config.status/config.status

CentOS 7 amd64 build: Failed (click for details)

Make failed for CentOS 7 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI005BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory `/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function 'resolver_cb_socket_writable':
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
lib/resolver.c:79:3: error: 'thread_add_write' undeclared (first use in this function)
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ';' at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input

CentOS 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI005BUILD/config.status/config.status
CentOS 7 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI005BUILD/config.log/config.log.gz

Ubuntu 18.04 i386 build: Failed (click for details) Ubuntu 18.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18I386BUILD/config.log/config.log.gz Ubuntu 18.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18I386BUILD/config.status/config.status

Make failed for Ubuntu 18.04 i386 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/U18I386BUILD/ErrorLog/log_make.txt)

make[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c: In function resolver_cb_socket_writable:
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 
lib/resolver.c:79:3: error: thread_add_write undeclared (first use in this function); did you mean thread_cmd_init?
lib/resolver.c:79:3: note: each undeclared identifier is reported only once for each function it appears in
lib/resolver.c:79:3: error: expected ; at end of input
lib/resolver.c:79:3: error: expected declaration or statement at end of input
NetBSD 8 amd64 build: Failed (click for details) NetBSD 8 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI012BUILD/config.log/config.log.gz

Make failed for NetBSD 8 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI012BUILD/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:287:0: error: unterminated argument list invoking macro "thread_add_write"
 }
 ^
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect
gmake[1]: *** [Makefile:15501: vtysh/vtysh_cmd.c] Error 1
lib/resolver.c: In function 'resolver_cb_socket_writable':

NetBSD 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI012BUILD/config.status/config.status

OpenBSD 6 amd64 build: Failed (click for details)

Make failed for OpenBSD 6 amd64 build:
(see full Make log at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI011BUILD/ErrorLog/log_make.txt)

gmake  all-am
gmake[1]: Entering directory '/home/ci/cibuild.636/frr-source'
lib/resolver.c:79:3: error: unterminated function-like macro invocation
vtysh/../lib/thread.h:  CC       lib/debug.lo
197:9: note: macro 'thread_add_write' defined here
#define thread_add_write(m,f,a,v,t)      _xref_t_a(read_write, WRITE, m,f,a,v,t)
1 error generated.
File: lib/resolver.c failed to compile:
when extracting cli from it please inspect

OpenBSD 6 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI011BUILD/config.status/config.status
OpenBSD 6 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-636/artifact/CI011BUILD/config.log/config.log.gz

@LabN-CI
Copy link
Collaborator

LabN-CI commented Oct 7, 2021 •
edited
Loading

Outdated results 💚

Basic BGPD CI results: SUCCESS, 0 tests failed

_ _
Result SUCCESS git merge/9763 22e5a7a
Date 10/07/2021
Start 08:18:14
Finish 08:44:35
Run-Time 26:21
Total 1813
Pass 1813
Fail 0
Valgrind-Errors 0
Valgrind-Loss 0
Details vncregress-2021-10-07-08:18:14.txt
Log autoscript-2021-10-07-08:19:28.log.bz2
Memory 508 494 430

For details, please contact louberger

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-637/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 4: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 4: No useful log found
Topotests Ubuntu 18.04 arm8 part 7: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 7: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests debian 10 amd64 part 6: Failed (click for details) Topotests debian 10 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests Ubuntu 18.04 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18AMD64-637/test

Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 12:47:08.092 LDP: sync: ldp_sync_fsm_state_req: interface r1-eth1 (6) proto static\n2021/10/07 12:47:08.092 LDP: sync: send_ldp_sync_state_update: interface r1-eth1 (6), sync_start=1\n2021/10/07 12:47:08.127 LDP: send_packet: error sending packet to 2.2.2.2: Network is unreachable\n2021/10/07 12:47:09.224 LDP: zebra[in]: route add 10.0.1.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 12:47:09.224 LDP: zebra[in]: route add 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 12:47:09.224 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 12:47:09.225 LDP: zebra[out]: prefix 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 labels 17/- (add)\n2021/10/07 12:47:13.038 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 12:47:13.101 LDP: adj_new: lsr-id 3.3.3.3, iface r1-eth2\n2021/10/07 12:47:13.101 LDP: sync: ldp_sync_fsm_adj_event: event IFACE SYNC START (ADJ NEW), adj iface r1-eth2 (7) lsr-id 3.3.3.3 source address 10.0.2.3 transport address 3.3.3.3\n2021/10/07 12:47:13.101 LDP: sync: ldp_sync_fsm: event IFACE SYNC START (ADJ NEW) resulted in action NOTHING for interface r1-eth2, remaining in state NOT ACHIEVED\n2021/10/07 12:47:13.101 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 12:47:13.129 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 12:47:13.130 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 12:47:13.130 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 12:47:13.130 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 12:47:13.130 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 12:47:13.144 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 12:47:13.161 LDP: waiting for children to terminate\n2021/10/07 12:47:13.161 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-637/artifact/TOPO7U18AMD64/ErrorLog/log_topotests.txt

Topotests debian 10 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-637/test

Topology Tests failed for Topotests debian 10 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 12:45:14.675 LDP: send_packet: error sending packet to 2.2.2.2: Network is unreachable\n2021/10/07 12:45:15.728 LDP: zebra[in]: route add 10.0.1.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 12:45:15.728 LDP: zebra[in]: route add 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 12:45:15.728 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 12:45:15.728 LDP: zebra[out]: prefix 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 labels 17/- (add)\n2021/10/07 12:45:18.267 LDP: adj_new: lsr-id 3.3.3.3, iface r1-eth2\n2021/10/07 12:45:18.267 LDP: sync: ldp_sync_fsm_adj_event: event IFACE SYNC START (ADJ NEW), adj iface r1-eth2 (7) lsr-id 3.3.3.3 source address 10.0.2.3 transport address 3.3.3.3\n2021/10/07 12:45:18.267 LDP: sync: ldp_sync_fsm: event IFACE SYNC START (ADJ NEW) resulted in action NOTHING for interface r1-eth2, remaining in state NOT ACHIEVED\n2021/10/07 12:45:18.267 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 12:45:18.349 LDP: sync: ldp_sync_fsm_state_req: interface r1-eth2 (7) proto static\n2021/10/07 12:45:18.349 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 12:45:18.740 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 12:45:19.676 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 12:45:19.676 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 12:45:19.676 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 12:45:19.676 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 12:45:19.676 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 12:45:19.676 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 12:45:19.690 LDP: waiting for children to terminate\n2021/10/07 12:45:19.690 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-637/artifact/TOPO7DEB10AMD64/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-637/test

Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 12:47:42.651 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 12:47:43.354 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 12:47:44.571 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 12:47:44.572 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 12:47:44.572 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 12:47:44.572 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 12:47:44.572 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 12:47:44.675 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 12:47:44.675 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 12:47:44.675 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 12:47:44.675 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 12:47:44.675 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 12:47:44.675 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 12:47:44.679 LDP: waiting for children to terminate\n2021/10/07 12:47:44.679 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-637/artifact/TOPO7U18I386/ErrorLog/log_topotests.txt

Successful on other platforms/tests
  • Topotests Ubuntu 18.04 i386 part 8
  • Topotests Ubuntu 18.04 i386 part 3
  • Topotests debian 10 amd64 part 8
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 amd64 part 2
  • Topotests debian 10 amd64 part 3
  • Addresssanitizer topotests part 0
  • Topotests Ubuntu 18.04 arm8 part 9
  • Addresssanitizer topotests part 4
  • Topotests Ubuntu 18.04 arm8 part 3
  • Debian 9 deb pkg check
  • Topotests debian 10 amd64 part 9
  • IPv4 protocols on Ubuntu 18.04
  • Addresssanitizer topotests part 1
  • Topotests Ubuntu 18.04 i386 part 4
  • Topotests Ubuntu 18.04 i386 part 9
  • Topotests debian 10 amd64 part 4
  • Topotests debian 10 amd64 part 2
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 amd64 part 9
  • Topotests Ubuntu 18.04 arm8 part 0
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests Ubuntu 18.04 arm8 part 2
  • Static analyzer (clang)
  • Topotests debian 10 amd64 part 0
  • Addresssanitizer topotests part 7
  • Topotests Ubuntu 18.04 amd64 part 5
  • Ubuntu 20.04 deb pkg check
  • IPv4 ldp protocol on Ubuntu 18.04
  • Debian 10 deb pkg check
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests debian 10 amd64 part 1
  • Addresssanitizer topotests part 5
  • Topotests Ubuntu 18.04 i386 part 1
  • Topotests Ubuntu 18.04 arm8 part 1
  • Topotests Ubuntu 18.04 amd64 part 0
  • Addresssanitizer topotests part 3
  • Topotests Ubuntu 18.04 i386 part 5
  • Addresssanitizer topotests part 2
  • Topotests debian 10 amd64 part 5
  • Topotests Ubuntu 18.04 amd64 part 4
  • CentOS 7 rpm pkg check
  • Fedora 29 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 3
  • Topotests Ubuntu 18.04 i386 part 2
  • Addresssanitizer topotests part 8
  • Topotests Ubuntu 18.04 arm8 part 8
  • Ubuntu 18.04 deb pkg check
  • Topotests Ubuntu 18.04 i386 part 0
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 amd64 part 1

@ton31337 ton31337 force-pushed the fix/more_thread_null branch 3 times, most recently from 8fa8abf to 6764447 Compare October 7, 2021 17:52
@qlyoung
Copy link
Member

qlyoung commented Oct 7, 2021

@frrbot rereview

@LabN-CI
Copy link
Collaborator

LabN-CI commented Oct 7, 2021 •
edited
Loading

Outdated results 💚

Basic BGPD CI results: SUCCESS, 0 tests failed

_ _
Result SUCCESS git merge/9763 6764447
Date 10/07/2021
Start 15:28:05
Finish 15:54:43
Run-Time 26:38
Total 1813
Pass 1813
Fail 0
Valgrind-Errors 0
Valgrind-Loss 0
Details vncregress-2021-10-07-15:28:05.txt
Log autoscript-2021-10-07-15:29:14.log.bz2
Memory 513 494 424

For details, please contact louberger

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-654/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests Ubuntu 18.04 amd64 part 1: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 1: No useful log found
Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-654/test

Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:48:51.073 LDP: send_packet: error sending packet to 2.2.2.2: Network is unreachable\n2021/10/07 18:48:52.192 LDP: zebra[in]: route add 10.0.1.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:48:52.192 LDP: zebra[in]: route add 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:48:52.192 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:48:52.192 LDP: zebra[out]: prefix 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 labels 17/- (add)\n2021/10/07 18:48:54.769 LDP: adj_new: lsr-id 3.3.3.3, iface r1-eth2\n2021/10/07 18:48:54.769 LDP: sync: ldp_sync_fsm_adj_event: event IFACE SYNC START (ADJ NEW), adj iface r1-eth2 (7) lsr-id 3.3.3.3 source address 10.0.2.3 transport address 3.3.3.3\n2021/10/07 18:48:54.769 LDP: sync: ldp_sync_fsm: event IFACE SYNC START (ADJ NEW) resulted in action NOTHING for interface r1-eth2, remaining in state NOT ACHIEVED\n2021/10/07 18:48:54.769 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 18:48:54.869 LDP: sync: ldp_sync_fsm_state_req: interface r1-eth2 (7) proto static\n2021/10/07 18:48:54.869 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 18:48:55.201 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:48:56.074 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:48:56.074 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:48:56.074 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:48:56.074 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:48:56.074 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:48:56.075 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:48:56.079 LDP: waiting for children to terminate\n2021/10/07 18:48:56.079 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-654/artifact/TOPO7U18I386/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18AMD64-654/test

Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:45:50.177 LDP: send_packet: error sending packet to 2.2.2.2: Network is unreachable\n2021/10/07 18:45:51.874 LDP: zebra[in]: route add 10.0.1.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:45:51.874 LDP: zebra[in]: route add 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:45:51.874 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:45:51.875 LDP: zebra[out]: prefix 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 labels 17/- (add)\n2021/10/07 18:45:53.382 LDP: adj_new: lsr-id 3.3.3.3, iface r1-eth2\n2021/10/07 18:45:53.382 LDP: sync: ldp_sync_fsm_adj_event: event IFACE SYNC START (ADJ NEW), adj iface r1-eth2 (7) lsr-id 3.3.3.3 source address 10.0.2.3 transport address 3.3.3.3\n2021/10/07 18:45:53.382 LDP: sync: ldp_sync_fsm: event IFACE SYNC START (ADJ NEW) resulted in action NOTHING for interface r1-eth2, remaining in state NOT ACHIEVED\n2021/10/07 18:45:53.382 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 18:45:53.489 LDP: sync: ldp_sync_fsm_state_req: interface r1-eth2 (7) proto static\n2021/10/07 18:45:53.489 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 18:45:53.884 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:45:55.179 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:45:55.179 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:45:55.179 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:45:55.179 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:45:55.179 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:45:55.187 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:45:55.193 LDP: waiting for children to terminate\n2021/10/07 18:45:55.193 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-654/artifact/TOPO7U18AMD64/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 arm8 part 7: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 7: No useful log found
Topotests debian 10 amd64 part 6: Failed (click for details) Topotests debian 10 amd64 part 6: No useful log found
Topotests debian 10 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-654/test

Topology Tests failed for Topotests debian 10 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:42:33.262 LDP: send_packet: error sending packet to 2.2.2.2: Network is unreachable\n2021/10/07 18:42:34.708 LDP: zebra[in]: route add 10.0.1.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:42:34.708 LDP: zebra[in]: route add 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:42:34.708 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:42:34.709 LDP: zebra[out]: prefix 2.2.2.2/32 nexthop 10.0.1.2 ifindex 6 labels 17/- (add)\n2021/10/07 18:42:37.771 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:42:37.987 LDP: adj_new: lsr-id 3.3.3.3, iface r1-eth2\n2021/10/07 18:42:37.987 LDP: sync: ldp_sync_fsm_adj_event: event IFACE SYNC START (ADJ NEW), adj iface r1-eth2 (7) lsr-id 3.3.3.3 source address 10.0.2.3 transport address 3.3.3.3\n2021/10/07 18:42:37.987 LDP: sync: ldp_sync_fsm: event IFACE SYNC START (ADJ NEW) resulted in action NOTHING for interface r1-eth2, remaining in state NOT ACHIEVED\n2021/10/07 18:42:37.987 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 18:42:38.057 LDP: sync: ldp_sync_fsm_state_req: interface r1-eth2 (7) proto static\n2021/10/07 18:42:38.057 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 18:42:38.263 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:42:38.263 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:42:38.263 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:42:38.263 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:42:38.263 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:42:38.266 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:42:38.287 LDP: waiting for children to terminate\n2021/10/07 18:42:38.287 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-654/artifact/TOPO7DEB10AMD64/ErrorLog/log_topotests.txt

Successful on other platforms/tests
  • Topotests Ubuntu 18.04 arm8 part 9
  • Ubuntu 18.04 deb pkg check
  • Debian 9 deb pkg check
  • Addresssanitizer topotests part 1
  • Ubuntu 20.04 deb pkg check
  • Topotests Ubuntu 18.04 i386 part 4
  • IPv4 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 i386 part 9
  • Topotests Ubuntu 18.04 amd64 part 9
  • Topotests Ubuntu 18.04 i386 part 8
  • Topotests Ubuntu 18.04 i386 part 3
  • Addresssanitizer topotests part 8
  • Debian 10 deb pkg check
  • Addresssanitizer topotests part 4
  • Topotests Ubuntu 18.04 arm8 part 3
  • Addresssanitizer topotests part 5
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests debian 10 amd64 part 1
  • Topotests debian 10 amd64 part 4
  • Topotests Ubuntu 18.04 arm8 part 0
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests debian 10 amd64 part 2
  • Addresssanitizer topotests part 0
  • Topotests debian 10 amd64 part 3
  • Static analyzer (clang)
  • Topotests Ubuntu 18.04 amd64 part 5
  • Addresssanitizer topotests part 2
  • IPv4 ldp protocol on Ubuntu 18.04
  • Topotests debian 10 amd64 part 5
  • Topotests Ubuntu 18.04 arm8 part 2
  • Ubuntu 16.04 deb pkg check
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 amd64 part 4
  • Topotests Ubuntu 18.04 i386 part 1
  • Topotests Ubuntu 18.04 i386 part 2
  • Topotests Ubuntu 18.04 arm8 part 1
  • Addresssanitizer topotests part 3
  • Addresssanitizer topotests part 7
  • Topotests Ubuntu 18.04 arm8 part 8
  • Topotests debian 10 amd64 part 0
  • Topotests Ubuntu 18.04 i386 part 0
  • Addresssanitizer topotests part 6
  • Topotests debian 10 amd64 part 9
  • Fedora 29 rpm pkg check
  • CentOS 7 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 3
  • Topotests Ubuntu 18.04 amd64 part 0
  • Topotests Ubuntu 18.04 amd64 part 2
  • Topotests debian 10 amd64 part 8
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 arm8 part 4

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

Test incomplete. See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-655/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Incomplete

Topotests debian 10 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-655/test

Topology Tests failed for Topotests debian 10 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 19:01:36.675 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 19:01:37.522 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 19:01:38.976 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 19:01:38.977 LDP: waiting for children to terminate\n2021/10/07 19:01:38.977 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-655/artifact/TOPO7DEB10AMD64/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests debian 10 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-655/test

Topology Tests failed for Topotests debian 10 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 19:01:36.675 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 19:01:37.522 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 19:01:38.591 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 19:01:38.972 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 19:01:38.972 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 19:01:38.976 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 19:01:38.977 LDP: waiting for children to terminate\n2021/10/07 19:01:38.977 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-655/artifact/TOPO7DEB10AMD64/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 7: Incomplete (check logs for details)
Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-655/test

Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:47:35.764 LDP: nbr_new: lsr-id 3.3.3.3 transport-address 3.3.3.3\n2021/10/07 18:47:36.609 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:47:37.763 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:47:37.763 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:47:37.763 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:47:37.763 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:47:37.764 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 18:47:38.241 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:47:38.241 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:47:38.241 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 18:47:38.241 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 18:47:38.241 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 18:47:38.242 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:47:38.252 LDP: waiting for children to terminate\n2021/10/07 18:47:38.252 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-655/artifact/TOPO7U18I386/ErrorLog/log_topotests.txt

Topotests debian 10 amd64 part 6: Failed (click for details) Topotests debian 10 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 amd64 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18AMD64-655/test

Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:46:21.175 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 18:46:21.482 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:46:22.287 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:46:22.288 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:46:22.288 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:46:22.288 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:46:22.288 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 18:46:22.751 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:46:22.751 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:46:22.751 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 18:46:22.751 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 18:46:22.751 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 18:46:22.754 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:46:22.770 LDP: waiting for children to terminate\n2021/10/07 18:46:22.770 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-655/artifact/TOPO7U18AMD64/ErrorLog/log_topotests.txt

Topotests debian 10 amd64 part 9: Failed (click for details) Topotests debian 10 amd64 part 9: No useful log found
Successful on other platforms/tests
  • Topotests Ubuntu 18.04 amd64 part 1
  • Debian 9 deb pkg check
  • Ubuntu 18.04 deb pkg check
  • Addresssanitizer topotests part 1
  • Ubuntu 20.04 deb pkg check
  • Topotests Ubuntu 18.04 i386 part 4
  • Topotests Ubuntu 18.04 i386 part 9
  • IPv4 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 amd64 part 9
  • Addresssanitizer topotests part 8
  • Topotests Ubuntu 18.04 i386 part 3
  • Topotests Ubuntu 18.04 i386 part 8
  • Debian 10 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 3
  • Addresssanitizer topotests part 4
  • Topotests debian 10 amd64 part 1
  • Addresssanitizer topotests part 5
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests debian 10 amd64 part 4
  • Topotests Ubuntu 18.04 arm8 part 0
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests debian 10 amd64 part 2
  • Addresssanitizer topotests part 0
  • Static analyzer (clang)
  • Topotests debian 10 amd64 part 3
  • IPv4 ldp protocol on Ubuntu 18.04
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 5
  • Topotests debian 10 amd64 part 5
  • Topotests Ubuntu 18.04 arm8 part 2
  • Topotests Ubuntu 18.04 i386 part 1
  • Topotests Ubuntu 18.04 amd64 part 4
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 i386 part 2
  • Addresssanitizer topotests part 3
  • Topotests Ubuntu 18.04 arm8 part 1
  • Addresssanitizer topotests part 7
  • Topotests Ubuntu 18.04 arm8 part 8
  • Topotests debian 10 amd64 part 0
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 i386 part 0
  • Fedora 29 rpm pkg check
  • CentOS 7 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 0
  • Topotests Ubuntu 18.04 amd64 part 3
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 amd64 part 2
  • Topotests debian 10 amd64 part 8
  • Topotests Ubuntu 18.04 arm8 part 9
  • Topotests Ubuntu 18.04 arm8 part 4
  • Addresssanitizer topotests part 2

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 7, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-656/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests debian 10 amd64 part 7: Failed (click for details) Topotests debian 10 amd64 part 7: No useful log found
Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 6: Failed (click for details) Topotests Ubuntu 18.04 i386 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 6: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 6: No useful log found
Topotests Ubuntu 18.04 arm8 part 7: Failed (click for details) Topotests Ubuntu 18.04 arm8 part 7: No useful log found
Topotests debian 10 amd64 part 6: Failed (click for details) Topotests debian 10 amd64 part 6: No useful log found
Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-656/test

Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7:

r1: Daemon ldpd not running

From frr r1 ldpd log file:
b'2021/10/07 18:48:24.656 LDP: sync: send_ldp_sync_state_update: interface r1-eth2 (7), sync_start=1\n2021/10/07 18:48:25.367 LDP: adj_new: lsr-id 2.2.2.2, source 2.2.2.2\n2021/10/07 18:48:26.568 LDP: zebra[in]: route add 10.0.2.0/24 nexthop 0.0.0.0 ifindex 0 (connected)\n2021/10/07 18:48:26.568 LDP: zebra[in]: route add 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:48:26.568 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.1.2 ifindex 6 (isis)\n2021/10/07 18:48:26.568 LDP: zebra[in]: route add 10.0.3.0/24 nexthop 10.0.2.3 ifindex 7 (isis)\n2021/10/07 18:48:26.568 LDP: zebra[out]: prefix 3.3.3.3/32 nexthop 10.0.2.3 ifindex 7 labels 18/- (add)\n2021/10/07 18:48:26.772 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 2.2.2.2 from PRESENT to INITIALIZED\n2021/10/07 18:48:26.772 LDP: nbr_fsm: event ADJACENCY MATCHED resulted in action NOTHING and changing state for lsr-id 3.3.3.3 from PRESENT to INITIALIZED\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 2.2.2.2 announced the Dynamic Capability Announcement capability\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 2.2.2.2 announced the Typed Wildcard FEC capability\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 2.2.2.2 announced the Unrecognized Notification capability\n2021/10/07 18:48:26.772 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 2.2.2.2 from INITIALIZED to OPENREC\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 3.3.3.3 announced the Dynamic Capability Announcement capability\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 3.3.3.3 announced the Typed Wildcard FEC capability\n2021/10/07 18:48:26.772 LDP: recv_init: lsr-id 3.3.3.3 announced the Unrecognized Notification capability\n2021/10/07 18:48:26.772 LDP: nbr_fsm: event INIT RECEIVED resulted in action SEND INIT AND KEEPALIVE and changing state for lsr-id 3.3.3.3 from INITIALIZED to OPENREC\n2021/10/07 18:48:26.777 LDP: nbr_fsm: event KEEPALIVE RECEIVED resulted in action START NEIGHBOR SESSION and changing state for lsr-id 2.2.2.2 from OPENREC to OPERATIONAL\n2021/10/07 18:48:26.779 LDP: waiting for children to terminate\n2021/10/07 18:48:26.779 LDP: terminating\n'

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-656/artifact/TOPO7U18I386/ErrorLog/log_topotests.txt

Topotests Ubuntu 18.04 amd64 part 7: Failed (click for details) Topotests Ubuntu 18.04 amd64 part 7: No useful log found
Topotests Ubuntu 18.04 amd64 part 3: Failed (click for details)

Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TP3U1804AMD64-656/test

Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 3:

r1: Daemon zebra not running

From frr r1 zebra log file:
b''
r2: Daemon zebra not running

From frr r2 zebra log file:
b''
P1: Daemon zebra not running

From frr P1 zebra log file:
b''
PE1: Daemon zebra not running

From frr PE1 zebra log file:
b''
PE2: Daemon zebra not running

From frr PE2 zebra log file:
b''
host1: Daemon zebra not running

From frr host1 zebra log file:
b''
host2: Daemon zebra not running

From frr host2 zebra log file:
b''
r1: Daemon zebra not running

From frr r1 zebra log file:
b''
r2: Daemon zebra not running

From frr r2 zebra log file:
b''
r3: Daemon zebra not running

From frr r3 zebra log file:
b''
r4: Daemon zebra not running

From frr r4 zebra log file:
b''
r5: Daemon zebra not running

From frr r5 zebra log file:
b''
r1: Daemon zebra not running

From frr r1 zebra log file:
b''

see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-656/artifact/TP3U1804AMD64/ErrorLog/log_topotests.txt

Successful on other platforms/tests
  • Debian 9 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 1
  • Addresssanitizer topotests part 1
  • Ubuntu 20.04 deb pkg check
  • Topotests Ubuntu 18.04 i386 part 4
  • Ubuntu 18.04 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests Ubuntu 18.04 i386 part 9
  • IPv4 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 arm8 part 0
  • Topotests Ubuntu 18.04 i386 part 8
  • Topotests Ubuntu 18.04 amd64 part 9
  • Topotests Ubuntu 18.04 i386 part 3
  • Addresssanitizer topotests part 8
  • Debian 10 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 3
  • Addresssanitizer topotests part 4
  • Addresssanitizer topotests part 5
  • Topotests debian 10 amd64 part 1
  • Topotests debian 10 amd64 part 4
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests debian 10 amd64 part 2
  • Addresssanitizer topotests part 0
  • Topotests debian 10 amd64 part 3
  • Static analyzer (clang)
  • Topotests debian 10 amd64 part 0
  • IPv4 ldp protocol on Ubuntu 18.04
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 5
  • Topotests Ubuntu 18.04 arm8 part 2
  • Topotests debian 10 amd64 part 5
  • Topotests Ubuntu 18.04 i386 part 1
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 amd64 part 4
  • Topotests Ubuntu 18.04 i386 part 2
  • Addresssanitizer topotests part 7
  • Topotests Ubuntu 18.04 arm8 part 8
  • Topotests Ubuntu 18.04 arm8 part 1
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 i386 part 0
  • Topotests debian 10 amd64 part 9
  • Addresssanitizer topotests part 3
  • Topotests Ubuntu 18.04 amd64 part 2
  • CentOS 7 rpm pkg check
  • Fedora 29 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 0
  • Topotests debian 10 amd64 part 8
  • Topotests Ubuntu 18.04 arm8 part 4
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 arm8 part 9
  • Addresssanitizer topotests part 2

@ton31337
tests: Do not explicitly set the thread pointer to NULL
1a8e5ae 
FRR should only ever use the appropriate THREAD_ON/THREAD_OFF
semantics.  This is espacially true for the functions we
end up calling the thread for.

Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
@ton31337
ospfd: Do not explicitly set the thread pointer to NULL
3063485 
FRR should only ever use the appropriate THREAD_ON/THREAD_OFF
semantics.  This is espacially true for the functions we
end up calling the thread for.

Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
@ton31337
isisd: Do not explicitly set the thread pointer to NULL
ae84497 
FRR should only ever use the appropriate THREAD_ON/THREAD_OFF
semantics.  This is espacially true for the functions we
end up calling the thread for.

Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
@ton31337
ospf6d: Do not explicitly set the thread pointer to NULL
d573b8f 
FRR should only ever use the appropriate THREAD_ON/THREAD_OFF
semantics.  This is espacially true for the functions we
end up calling the thread for.

Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
@ton31337 ton31337 force-pushed the fix/more_thread_null branch from 6764447 to d573b8f Compare October 8, 2021 05:56
@frrbot frrbot bot added isis ospf ospfv3 tests Topotests, make check, etc labels Oct 8, 2021
@LabN-CI
Copy link
Collaborator

LabN-CI commented Oct 8, 2021

💚 Basic BGPD CI results: SUCCESS, 0 tests failed

Results table
_ _
Result SUCCESS git merge/9763 d573b8f
Date 10/08/2021
Start 02:22:41
Finish 02:48:57
Run-Time 26:16
Total 1813
Pass 1813
Fail 0
Valgrind-Errors 0
Valgrind-Loss 0
Details vncregress-2021-10-08-02:22:41.txt
Log autoscript-2021-10-08-02:23:49.log.bz2
Memory 516 501 426

For details, please contact louberger

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 8, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-660/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Failed

Ubuntu 16.04 i386 build: Failed (click for details) Ubuntu 16.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-660/artifact/U1604I386/ErrorLog/ Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-660/artifact/U1604I386/config.status/config.status Ubuntu 16.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-660/artifact/U1604I386/config.log/config.log.gz Ubuntu 16.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-660/artifact/U1604I386/frr.xref.xz/frr.xref.xz Ubuntu 16.04 i386 build: No useful log found
Successful on other platforms/tests
  • Ubuntu 16.04 amd64 build
  • FreeBSD 12 amd64 build
  • Ubuntu 16.04 arm8 build
  • CentOS 7 amd64 build
  • Ubuntu 18.04 i386 build
  • NetBSD 8 amd64 build
  • Ubuntu 18.04 arm7 build
  • Ubuntu 18.04 arm8 build
  • CentOS 8 amd64 build
  • Debian 11 amd64 build
  • Debian 10 amd64 build
  • Fedora 29 amd64 build
  • OpenBSD 6 amd64 build
  • FreeBSD 11 amd64 build
  • Debian 9 amd64 build
  • Ubuntu 16.04 arm7 build
  • Ubuntu 20.04 amd64 build
  • Ubuntu 18.04 ppc64le build
  • Ubuntu 18.04 amd64 build

@ton31337
Copy link
Member Author

ton31337 commented Oct 8, 2021

ci:rerun

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 8, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-664/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests debian 10 amd64 part 9: Failed (click for details) Topotests debian 10 amd64 part 9: No useful log found
Successful on other platforms/tests
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests Ubuntu 18.04 i386 part 9
  • Topotests debian 10 amd64 part 7
  • IPv4 protocols on Ubuntu 18.04
  • Static analyzer (clang)
  • Topotests Ubuntu 18.04 arm8 part 0
  • Debian 9 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 9
  • Addresssanitizer topotests part 8
  • Topotests debian 10 amd64 part 2
  • Debian 10 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests Ubuntu 18.04 amd64 part 6
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 amd64 part 1
  • Ubuntu 20.04 deb pkg check
  • Ubuntu 18.04 deb pkg check
  • Addresssanitizer topotests part 5
  • Topotests debian 10 amd64 part 6
  • Topotests debian 10 amd64 part 1
  • Topotests Ubuntu 18.04 arm8 part 1
  • Addresssanitizer topotests part 4
  • Addresssanitizer topotests part 0
  • Topotests debian 10 amd64 part 4
  • Topotests debian 10 amd64 part 3
  • Topotests Ubuntu 18.04 arm8 part 3
  • Addresssanitizer topotests part 1
  • Topotests Ubuntu 18.04 i386 part 4
  • Topotests Ubuntu 18.04 arm8 part 7
  • Addresssanitizer topotests part 9
  • Topotests debian 10 amd64 part 0
  • IPv4 ldp protocol on Ubuntu 18.04
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 2
  • Topotests debian 10 amd64 part 5
  • Topotests Ubuntu 18.04 i386 part 1
  • Addresssanitizer topotests part 7
  • Topotests Ubuntu 18.04 arm8 part 8
  • Topotests Ubuntu 18.04 i386 part 7
  • Topotests Ubuntu 18.04 i386 part 6
  • Topotests Ubuntu 18.04 i386 part 2
  • Topotests Ubuntu 18.04 amd64 part 5
  • Topotests Ubuntu 18.04 arm8 part 6
  • Topotests Ubuntu 18.04 amd64 part 7
  • Fedora 29 rpm pkg check
  • Topotests Ubuntu 18.04 i386 part 8
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 i386 part 3
  • Topotests Ubuntu 18.04 i386 part 0
  • Addresssanitizer topotests part 3
  • Topotests debian 10 amd64 part 8
  • Topotests Ubuntu 18.04 amd64 part 2
  • Topotests Ubuntu 18.04 arm8 part 4
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 amd64 part 4
  • CentOS 7 rpm pkg check
  • Topotests Ubuntu 18.04 arm8 part 9
  • Addresssanitizer topotests part 2
  • Topotests Ubuntu 18.04 amd64 part 3
  • Topotests Ubuntu 18.04 amd64 part 0

@ton31337
Copy link
Member Author

ton31337 commented Oct 8, 2021

ci:rerun

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 8, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-686/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Failed

OpenBSD 6 amd64 build: Failed (click for details)

DejaGNU Unittests (make check) failed for OpenBSD 6 amd64 build:
(see full PyTest log at https://ci1.netdef.org/browse/FRR-PULLREQ2-686/artifact/CI011BUILD/ErrorLog/log_pytests.txt)

=================================== FAILURES ===================================
_________________________ TestMpath.test_exit_cleanly __________________________
self = <test_mpath.TestMpath object at 0x14b9733702b0>
    def testfunction(self):
        self._run_tests()
        result = self.testresults[matchfunction]
        if result is not None:
>           frrsix.reraise(*result)
helpers/python/frrtest.py:108: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
helpers/python/frrsix.py:62: in reraise
    raise value
helpers/python/frrtest.py:82: in _run_tests
    test(self)
helpers/python/frrtest.py:100: in matchfunction
    method(self, *args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
self = <test_mpath.TestMpath object at 0x14b9733702b0>
    def _exit_cleanly(self):
        if self.exitcode != 0:
>           raise MultiTestFailure("Program did not terminate with exit code 0")
E           frrtest.MultiTestFailure: Program did not terminate with exit code 0
helpers/python/frrtest.py:90: MultiTestFailure
----------------------------- Captured stderr call -----------------------------
2021/10/08 11:18:42 [YAF85-253AP][EC 100663299] buffer_write: write error on fd 0: Bad file descriptor
2021/10/08 11:18:42 [X6B3Y-6W42R][EC 100663302] zclient_send_message: buffer_write failed to zclient fd 0, closing
___________________ TestMpath.test_bgp_maximum_paths_config ____________________
self = <test_mpath.TestMpath object at 0x14b87f9a1f28>
    def testfunction(self):
        self._run_tests()
        result = self.testresults[matchfunction]
        if result is not None:
>           frrsix.reraise(*result)
helpers/python/frrtest.py:108: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
helpers/python/frrsix.py:62: in reraise
    raise value
helpers/python/frrtest.py:82: in _run_tests
    test(self)
helpers/python/frrtest.py:100: in matchfunction
    method(self, *args, **kwargs)
helpers/python/frrtest.py:152: in _okfail
    self._onesimple(line)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
self = <test_mpath.TestMpath object at 0x14b9733702b0>
line = b'bgp maximum-paths config'
    def _onesimple(self, line):
        if type(line) is str:
            line = line.encode("utf8")
        idx = self.output.find(line)
        if idx != -1:
            self.output = self.output[idx + len(line) :]
        else:
>           raise MultiTestFailure("%r could not be found" % line)
E           frrtest.MultiTestFailure: b'bgp maximum-paths config' could not be found
helpers/python/frrtest.py:149: MultiTestFailure
__________________________ TestMpath.test_bgp_mp_list __________________________
self = <test_mpath.TestMpath object at 0x14b87f9a1da0>
    def testfunction(self):
        self._run_tests()
        result = self.testresults[matchfunction]
        if result is not None:
>           frrsix.reraise(*result)
helpers/python/frrtest.py:108: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
helpers/python/frrsix.py:62: in reraise
    raise value
helpers/python/frrtest.py:82: in _run_tests
    test(self)
helpers/python/frrtest.py:100: in matchfunction
    method(self, *args, **kwargs)
helpers/python/frrtest.py:152: in _okfail
    self._onesimple(line)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
self = <test_mpath.TestMpath object at 0x14b9733702b0>, line = b'bgp_mp_list'
    def _onesimple(self, line):
        if type(line) is str:
            line = line.encode("utf8")
        idx = self.output.find(line)
        if idx != -1:
            self.output = self.output[idx + len(line) :]
        else:
>           raise MultiTestFailure("%r could not be found" % line)
E           frrtest.MultiTestFailure: b'bgp_mp_list' could not be found
helpers/python/frrtest.py:149: MultiTestFailure
__________________ TestMpath.test_bgp_path_info_mpath_update ___________________
self = <test_mpath.TestMpath object at 0x14b9733846d8>
    def testfunction(self):
        self._run_tests()
        result = self.testresults[matchfunction]
        if result is not None:
>           frrsix.reraise(*result)
helpers/python/frrtest.py:108: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
helpers/python/frrsix.py:62: in reraise
    raise value
helpers/python/frrtest.py:82: in _run_tests
    test(self)
helpers/python/frrtest.py:100: in matchfunction
    method(self, *args, **kwargs)
helpers/python/frrtest.py:152: in _okfail

OpenBSD 6 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-686/artifact/CI011BUILD/config.status/config.status
OpenBSD 6 amd64 build: Unknown Log <config.log.gz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-686/artifact/CI011BUILD/config.log/config.log.gz
OpenBSD 6 amd64 build: Unknown Log <frr.xref.xz>
URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-686/artifact/CI011BUILD/frr.xref.xz/frr.xref.xz

Successful on other platforms/tests
  • Ubuntu 16.04 arm7 build
  • Ubuntu 18.04 arm7 build
  • Ubuntu 16.04 i386 build
  • CentOS 7 amd64 build
  • Ubuntu 16.04 arm8 build
  • Ubuntu 18.04 amd64 build
  • Debian 11 amd64 build
  • FreeBSD 11 amd64 build
  • NetBSD 8 amd64 build
  • FreeBSD 12 amd64 build
  • Ubuntu 16.04 amd64 build
  • Ubuntu 18.04 i386 build
  • Ubuntu 20.04 amd64 build
  • CentOS 8 amd64 build
  • Ubuntu 18.04 arm8 build
  • Debian 9 amd64 build
  • Ubuntu 18.04 ppc64le build
  • Debian 10 amd64 build
  • Fedora 29 amd64 build

@ton31337
Copy link
Member Author

ton31337 commented Oct 8, 2021

ci:rerun

@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented Oct 8, 2021 •
edited
Loading

Continuous Integration Result: FAILED

Continuous Integration Result: FAILED

See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-691/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Successful

Basic Tests: Failed

Topotests debian 10 amd64 part 1: Failed (click for details) Topotests debian 10 amd64 part 1: No useful log found
Successful on other platforms/tests
  • Fedora 29 rpm pkg check
  • Topotests Ubuntu 18.04 amd64 part 7
  • Addresssanitizer topotests part 3
  • Topotests Ubuntu 18.04 i386 part 5
  • Topotests Ubuntu 18.04 i386 part 0
  • Topotests Ubuntu 18.04 amd64 part 4
  • CentOS 7 rpm pkg check
  • Addresssanitizer topotests part 2
  • Topotests Ubuntu 18.04 amd64 part 0
  • Topotests debian 10 amd64 part 5
  • Addresssanitizer topotests part 1
  • Topotests Ubuntu 18.04 i386 part 4
  • Topotests Ubuntu 18.04 amd64 part 1
  • Topotests Ubuntu 18.04 i386 part 9
  • Topotests debian 10 amd64 part 7
  • Debian 9 deb pkg check
  • Addresssanitizer topotests part 8
  • Topotests Ubuntu 18.04 amd64 part 6
  • Topotests Ubuntu 18.04 arm8 part 8
  • Ubuntu 18.04 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 6
  • Addresssanitizer topotests part 6
  • Topotests Ubuntu 18.04 i386 part 2
  • Topotests Ubuntu 18.04 i386 part 7
  • Topotests Ubuntu 18.04 arm8 part 1
  • Topotests debian 10 amd64 part 6
  • Topotests Ubuntu 18.04 arm8 part 3
  • Topotests Ubuntu 18.04 amd64 part 2
  • Addresssanitizer topotests part 5
  • Topotests debian 10 amd64 part 4
  • Topotests Ubuntu 18.04 i386 part 3
  • Addresssanitizer topotests part 4
  • Topotests debian 10 amd64 part 3
  • Addresssanitizer topotests part 0
  • Topotests debian 10 amd64 part 8
  • Topotests debian 10 amd64 part 9
  • Topotests Ubuntu 18.04 arm8 part 9
  • Topotests Ubuntu 18.04 arm8 part 4
  • IPv6 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 amd64 part 3
  • Static analyzer (clang)
  • IPv4 protocols on Ubuntu 18.04
  • Topotests Ubuntu 18.04 arm8 part 2
  • Topotests debian 10 amd64 part 0
  • Topotests Ubuntu 18.04 arm8 part 7
  • Topotests Ubuntu 18.04 i386 part 6
  • Topotests Ubuntu 18.04 amd64 part 8
  • Topotests debian 10 amd64 part 2
  • Addresssanitizer topotests part 9
  • Topotests Ubuntu 18.04 arm8 part 0
  • IPv4 ldp protocol on Ubuntu 18.04
  • Ubuntu 16.04 deb pkg check
  • Topotests Ubuntu 18.04 arm8 part 5
  • Topotests Ubuntu 18.04 i386 part 8
  • Topotests Ubuntu 18.04 i386 part 1
  • Topotests Ubuntu 18.04 amd64 part 9
  • Addresssanitizer topotests part 7
  • Ubuntu 20.04 deb pkg check
  • Topotests Ubuntu 18.04 amd64 part 5
  • Debian 10 deb pkg check

@ton31337
Copy link
Member Author

ton31337 commented Oct 9, 2021

ci:rerun

@NetDEF-CI
Copy link
Collaborator

Continuous Integration Result: FAILED

Test incomplete. See below for issues.
CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-703/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Get source / Pull Request: Successful

Building Stage: Incomplete

Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 16.04 arm7 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 16.04 arm7 build: Incomplete (check logs for details)
Ubuntu 18.04 arm7 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 16.04 arm7 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 arm8 build: Incomplete (check logs for details)
Ubuntu 18.04 ppc64le build: Incomplete (check logs for details)
Ubuntu 16.04 arm7 build: Incomplete (check logs for details)
Ubuntu 18.04 arm7 build: Incomplete (check logs for details)
Ubuntu 16.04 arm8 build: Incomplete (check logs for details)
Successful on other platforms/tests
  • CentOS 8 amd64 build
  • Fedora 29 amd64 build
  • Debian 9 amd64 build
  • Ubuntu 20.04 amd64 build
  • Debian 10 amd64 build
  • CentOS 7 amd64 build
  • Debian 11 amd64 build
  • Ubuntu 16.04 i386 build
  • Ubuntu 16.04 amd64 build
  • Ubuntu 18.04 amd64 build
  • FreeBSD 11 amd64 build
  • OpenBSD 6 amd64 build
  • NetBSD 8 amd64 build
  • FreeBSD 12 amd64 build
  • Ubuntu 18.04 i386 build
### Basic Tests: Incomplete

@ton31337
Copy link
Member Author

ci:rerun

@ton31337 ton31337 requested a review from idryzhov October 11, 2021 13:58
riw777
riw777 approved these changes Oct 12, 2021
View reviewed changes
Copy link
Member

@riw777 riw777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@riw777 riw777 merged commit 0f96b7e into FRRouting:master Oct 12, 2021
@ton31337 ton31337 deleted the fix/more_thread_null branch October 12, 2021 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@riw777 riw777 riw777 approved these changes

@idryzhov idryzhov Awaiting requested review from idryzhov

Assignees
No one assigned
Labels
cleanup isis ospf ospfv3 tests Topotests, make check, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@ton31337 @LabN-CI @idryzhov @NetDEF-CI @qlyoung @riw777