arding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_0:ping to leaf_2_2:fGzEyK1x via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_2
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_0:ping to leaf_2_0:Mfuagj0V via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_1:r5EJLrca via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_0:jklz5C4I via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_2:ping to leaf_2_1:S671I3Yz via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_1:ping to leaf_2_0:BKuOFncF via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_1:r5EJLrca via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_2:ping to leaf_2_0:namzXfxd via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_2:ping to leaf_2_1:S671I3Yz via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_1:ping to leaf_2_2:gAy6bCYt via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_2
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_0:jklz5C4I via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_1:r5EJLrca via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from leaf_0_0:ping to leaf_2_0:Mfuagj0V via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_0
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_1:r5EJLrca via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
TRACE INFO 2023/12/04 03:30:38 --- Received data length 0 from backbone_0:ping to leaf_2_1:r5EJLrca via backbone_0
TRACE INFO 2023/12/04 03:30:38     Forwarding data length 0 via leaf_2_1
panic: close of nil channel
goroutine 1996 [running]:
github.com/ansible/receptor/pkg/utils.(*Broker).start(0x3f3c196600)
	/builddir/build/BUILD/receptor-1.4.3/_build/src/github.com/ansible/receptor/pkg/utils/broker.go:51 +0x120
created by github.com/ansible/receptor/pkg/utils.NewBroker in goroutine 1995
	/builddir/build/BUILD/receptor-1.4.3/_build/src/github.com/ansible/receptor/pkg/utils/broker.go:31 +0x168
exit status 2
FAIL	github.com/ansible/receptor/pkg/netceptor	32.018s
error: Bad exit status from /var/tmp/rpm-tmp.s60CF7 (%check)
    Bad exit status from /var/tmp/rpm-tmp.s60CF7 (%check)
RPM build errors:
Child return code was: 1
EXCEPTION: [Error()]
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.9/site-packages/mockbuild/util.py", line 600, in do_with_status
    raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode)
mockbuild.exception.Error: Command failed: 
 # bash --login -c /usr/bin/rpmbuild -ba --noprep --target riscv64 --nodeps /builddir/build/SPECS/receptor.spec