Package: src:mender-connect Version: 2.3.0+ds1-1 Severity: serious Tags: ftbfs trixie sid
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ please read notes at the end ] -------------------------------------------------------------------------------- [...] task-0: goroutine 89 [chan send (nil chan)]: task-0: github.com/mendersoftware/mender-connect/app.(*MenderShellDaemon).messageLoop(0xc00031aea0) task-0: /<<PKGBUILDDIR>>/_build/src/github.com/mendersoftware/mender-connect/app/daemon.go:215 +0x145 task-0: github.com/mendersoftware/mender-connect/app.TestMessageMainLoop.func1.1(0xc000260540) task-0: /<<PKGBUILDDIR>>/_build/src/github.com/mendersoftware/mender-connect/app/daemon_test.go:977 +0xaf task-0: testing.tRunner(0xc000260540, 0xc000091560) task-0: /usr/lib/go-1.24/src/testing/testing.go:1792 +0xf4 task-0: created by testing.(*T).Run in goroutine 88 task-0: /usr/lib/go-1.24/src/testing/testing.go:1851 +0x413 task-0: FAIL github.com/mendersoftware/mender-connect/app 86.019s task-0: ? github.com/mendersoftware/mender-connect/cli [no test files] -------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202504/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:mender-connect, so that this is still visible in the BTS web page for this package. Note: - Sorry for the lack of context. I had to trim the build log a lot because the SMTP server said it had too long lines. I've provided the full build log in the URL above anyway. - The package might not fail to build for everybody. In my setup, it fails very rarely on machines with 1 CPU and it fails 70% of the time on machines with 2 CPUs. Maybe this is a good hint. In either case, I offer a VM to test if required. Thanks.
