Your message dated Sun, 17 Jan 2021 15:42:30 +0000
with message-id <20210117154230.ga11...@esaurito.net>
and subject line Re: Bug#918526: mtail: FTBFS randomly
has caused the Debian Bug report #918526,
regarding mtail: FTBFS randomly / flaky autopkgtests
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.)


-- 
918526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mtail
Version: 3.0.0~rc16-1
Severity: important
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang 
--builddirectory=/<<PKGBUILDDIR>>/build
   dh_update_autotools_config -a -O--buildsystem=golang 
-O--builddirectory=/<<BUILDDIR>>/mtail-3.0.0\~rc16/build
   dh_autoreconf -a -O--buildsystem=golang 
-O--builddirectory=/<<BUILDDIR>>/mtail-3.0.0\~rc16/build
   dh_auto_configure -a -O--buildsystem=golang 
-O--builddirectory=/<<BUILDDIR>>/mtail-3.0.0\~rc16/build
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_build -- -ldflags " -X main.Version=3.0.0~rc16 -X 
main.Revision=3.0.0~rc16-1"
        cd build && go generate -v -ldflags " -X main.Version=3.0.0~rc16 -X 
main.Revision=3.0.0~rc16-1" github.com/google/mtail 
github.com/google/mtail/exporter github.com/google/mtail/logline 
github.com/google/mtail/metrics github.com/google/mtail/metrics/datum 
github.com/google/mtail/mtail github.com/google/mtail/tailer 
github.com/google/mtail/tailer/file github.com/google/mtail/testutil 
github.com/google/mtail/vm github.com/google/mtail/watcher
src/github.com/google/mtail/bench_test.go
src/github.com/google/mtail/ex_test.go
src/github.com/google/mtail/main.go
src/github.com/google/mtail/exporter/collectd.go
src/github.com/google/mtail/exporter/export.go

[... snipped ...]

    --- PASS: TestInstrs/cmp_ge (0.00s)
    --- PASS: TestInstrs/cmp_eq_string_string_true (0.00s)
    --- PASS: TestInstrs/cmp_eq_string_string_false (0.00s)
    --- PASS: TestInstrs/cmp_gt_int_float (0.00s)
    --- PASS: TestInstrs/cmp_gt_float_float (0.00s)
    --- PASS: TestInstrs/cmp_gt (0.00s)
    --- PASS: TestInstrs/cmp_gt_float_int (0.00s)
    --- PASS: TestInstrs/cmp_ne (0.00s)
    --- PASS: TestInstrs/cmp_le (0.00s)
    --- PASS: TestInstrs/cmp_eq (0.00s)
    --- PASS: TestInstrs/cmp_lt (0.00s)
=== RUN   TestDatumSetInstrs
--- PASS: TestDatumSetInstrs (0.00s)
=== RUN   TestStrptimeWithTimezone
--- PASS: TestStrptimeWithTimezone (0.00s)
=== RUN   TestStrptimeWithoutTimezone
--- PASS: TestStrptimeWithoutTimezone (0.00s)
=== RUN   TestDatumFetchInstrs
--- PASS: TestDatumFetchInstrs (0.00s)
=== RUN   TestWalkPanicsOnUnknown
--- PASS: TestWalkPanicsOnUnknown (0.00s)
PASS
ok      github.com/google/mtail/vm      0.098s
=== RUN   TestFakeWatcher
--- PASS: TestFakeWatcher (0.00s)
=== RUN   TestFakeWatcherUnwatchedFiles
--- PASS: TestFakeWatcherUnwatchedFiles (0.00s)
=== RUN   TestNoSuchHandle
--- PASS: TestNoSuchHandle (0.00s)
=== RUN   TestLogWatcher
--- PASS: TestLogWatcher (0.00s)
=== RUN   TestNewLogWatcherError
--- PASS: TestNewLogWatcherError (0.00s)
=== RUN   TestLogWatcherAddError
--- PASS: TestLogWatcherAddError (0.00s)
=== RUN   TestLogWatcherAddWhilePermissionDenied
--- PASS: TestLogWatcherAddWhilePermissionDenied (0.00s)
=== RUN   TestWatcherErrors
E1208 18:50:34.156489   32599 log_watcher.go:85] fsnotify error: Injected error 
for test
--- PASS: TestWatcherErrors (0.00s)
PASS
ok      github.com/google/mtail/watcher 0.013s
dh_auto_test: cd build && go test -vet=off -v -p 2 github.com/google/mtail 
github.com/google/mtail/exporter github.com/google/mtail/logline 
github.com/google/mtail/metrics github.com/google/mtail/metrics/datum 
github.com/google/mtail/mtail github.com/google/mtail/tailer 
github.com/google/mtail/tailer/file github.com/google/mtail/testutil 
github.com/google/mtail/vm github.com/google/mtail/watcher returned exit code 1
make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:18: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--------------------------------------------------------------------------------

This is just how the build ends and not necessarily the most relevant part,
so I've put a bunch of my build logs here:

https://people.debian.org/~sanvila/build-logs/mtail/

The test which usually fails for me is this one:

FAIL    github.com/google/mtail/tailer  0.018s

This does not seem to fail in reproducible-builds, but I found a build
failure here for mips64el, which is a release architecture:

https://buildd.debian.org/status/fetch.php?pkg=mtail&arch=mips64el&ver=3.0.0%7Erc16-1&stamp=1539028587&raw=0

The fact that I can reproduce this as well on amd64 suggests that this not 
arch-specific
but instead some sort of race condition.

If you need a test machine to reproduce this, please say so (contact me 
privately for details).

Thanks.

--- End Message ---
--- Begin Message ---
Hi,

On Sun, Jan 03, 2021 at 03:44:48PM +0100, Aurelien Jarno wrote:
> On 2020-04-24 17:15, Antoine Beaupre wrote:
> > Control: tags -1 +moreinfo
> > 
> > I have done some work on updating this package to latest upstream and
> > tweaking the tests a little. Could you see if this can be reproduced
> > again?
> 
> This is definitely reproducible:

I've uploaded 3.0.0~rc41-1 yesterday with the flaky tests fixed, and indeed
mtail built fine on all release architectures:

https://buildd.debian.org/status/package.php?p=mtail

I'm resolving the bug since I think it is fixed, of course please reopen if sth 
is amiss!

best,
Filippo

--- End Message ---

Reply via email to