Your message dated Wed, 25 May 2022 22:28:34 +0100
with message-id <813fb166-28b2-ac68-ddbd-279ad3977...@tina.pm>
and subject line Cannot reproduce
has caused the Debian Bug report #1010543,
regarding mtail: FTBFS on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1010543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mtail
Version: 3.0.0~rc48-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=mtail&arch=ppc64el&ver=3.0.0%7Erc48-4%2Bb1&stamp=1651446567&raw=0
=== RUN TestTestWakerWakes
--- PASS: TestTestWakerWakes (0.00s)
=== RUN TestTestWakerTwoWakees
--- PASS: TestTestWakerTwoWakees (0.00s)
=== RUN TestTestWakerTwoWakeups
--- PASS: TestTestWakerTwoWakeups (0.00s)
=== RUN TestTimedWakerWakes
--- PASS: TestTimedWakerWakes (0.02s)
PASS
ok github.com/google/mtail/internal/waker 0.027s
FAIL
dh_auto_test: error: cd build && go test -vet=off -v -p 4 -timeout 100s
github.com/google/mtail/cmd/mfmt github.com/google/mtail/cmd/mtail
github.com/google/mtail/internal/exporter
github.com/google/mtail/internal/logline
github.com/google/mtail/internal/metrics
github.com/google/mtail/internal/metrics/datum
github.com/google/mtail/internal/mtail
github.com/google/mtail/internal/mtail/golden
github.com/google/mtail/internal/runtime
github.com/google/mtail/internal/runtime/code
github.com/google/mtail/internal/runtime/compiler
github.com/google/mtail/internal/runtime/compiler/ast
github.com/google/mtail/internal/runtime/compiler/checker
github.com/google/mtail/internal/runtime/compiler/codegen
github.com/google/mtail/internal/runtime/compiler/errors
github.com/google/mtail/internal/runtime/compiler/opt
github.com/google/mtail/internal/runtime/compiler/parser
github.com/google/mtail/internal/runtime/compiler/position
github.com/google/mtail/internal/runtime/compiler/symbol
github.com/google/mtail/internal/runtime/compiler/types
github.com/google/mtail/internal/runtime/vm
github.com/google/mtail/internal/tailer
github.com/google/mtail/internal/tailer/logstream
github.com/google/mtail/internal/testutil
github.com/google/mtail/internal/waker returned exit code 1
make[1]: *** [debian/rules:34: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:25: binary-arch] Error 2
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Hi,
I am being unable to reproduce this bug. I have run the failing test
repeatedly 100 times (in a ppc64el porterbox) without a single failure,
and giving back the package resulted in a successful build.
My only guess is that this might have been related to a bug in some
dependency introduced during the binNMU that has since been corrected.
Considering all this, I am closing the bug. Please, reopen if needed.
--
Martina Ferrari (Tina)
--- End Message ---
