Your message dated Tue, 23 Aug 2016 22:53:28 +0000
with message-id <e1bckzu-0004tx...@franck.debian.org>
and subject line Bug#835057: fixed in golang-fsnotify 1.3.0-4
has caused the Debian Bug report #835057,
regarding golang-fsnotify: FTBFS too much often (failing tests)
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.)


-- 
835057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-fsnotify
Version: 1.3.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_testdir -i -O--buildsystem=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
        go install -v -p 1 github.com/fsnotify/fsnotify
golang.org/x/sys/unix
github.com/fsnotify/fsnotify
   dh_auto_test -i -O--buildsystem=golang
        go test -v -p 1 github.com/fsnotify/fsnotify
=== RUN   TestPollerWithBadFd
--- PASS: TestPollerWithBadFd (0.00s)

[... snipped ...]

        integration_test.go:602: event received: 
"/tmp/fsnotify922962472/TestFsnotifyEvents.testfile": RENAME
        integration_test.go:602: event received: 
"/tmp/fsnotify922962472/TestFsnotifyEvents.testfileRenamed": CREATE
        integration_test.go:602: event received: 
"/tmp/fsnotify922962472/TestFsnotifyEvents.testfile": RENAME
        integration_test.go:637: calling Close()
        integration_test.go:639: waiting for the event channel to become 
closed...
        integration_test.go:642: event channel closed
=== RUN   TestFsnotifyRenameToCreate
--- PASS: TestFsnotifyRenameToCreate (0.50s)
        integration_test.go:684: event received: 
"/tmp/fsnotify040233319/TestFsnotifyEvents.testfileRenamed": CREATE
        integration_test.go:713: calling Close()
        integration_test.go:715: waiting for the event channel to become 
closed...
        integration_test.go:718: event channel closed
=== RUN   TestFsnotifyRenameToOverwrite
--- PASS: TestFsnotifyRenameToOverwrite (0.50s)
        integration_test.go:772: event received: 
"/tmp/fsnotify422569009/TestFsnotifyEvents.testfileRenamed": CREATE
        integration_test.go:801: calling Close()
        integration_test.go:803: waiting for the event channel to become 
closed...
        integration_test.go:806: event channel closed
=== RUN   TestRemovalOfWatch
--- PASS: TestRemovalOfWatch (0.60s)
        integration_test.go:844: No event received, as expected.
=== RUN   TestFsnotifyAttrib
--- PASS: TestFsnotifyAttrib (1.50s)
        integration_test.go:901: event received: 
"/tmp/fsnotify018300782/TestFsnotifyAttrib.testfile": CHMOD
        integration_test.go:901: event received: 
"/tmp/fsnotify018300782/TestFsnotifyAttrib.testfile": WRITE
        integration_test.go:901: event received: 
"/tmp/fsnotify018300782/TestFsnotifyAttrib.testfile": CHMOD
        integration_test.go:979: calling Close()
        integration_test.go:981: waiting for the event channel to become 
closed...
        integration_test.go:984: event channel closed
=== RUN   TestFsnotifyClose
--- PASS: TestFsnotifyClose (0.05s)
=== RUN   TestFsnotifyFakeSymlink
--- PASS: TestFsnotifyFakeSymlink (0.50s)
        integration_test.go:1053: Created bogus symlink
        integration_test.go:1039: event received: 
"/tmp/fsnotify282172112/zzznew": CREATE
        integration_test.go:1075: calling Close()
=== RUN   TestCyclicSymlink
--- PASS: TestCyclicSymlink (0.50s)
=== RUN   TestConcurrentRemovalOfWatch
--- SKIP: TestConcurrentRemovalOfWatch (0.00s)
        integration_test.go:1131: regression test for race only present on 
darwin
=== RUN   TestClose
--- PASS: TestClose (0.00s)
=== RUN   TestRemoveWithClose
--- PASS: TestRemoveWithClose (0.01s)
FAIL
exit status 1
FAIL    github.com/fsnotify/fsnotify    13.464s
dh_auto_test: go test -v -p 1 github.com/fsnotify/fsnotify returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense, and the fact that I was
doing "dpkg-buildpackage -A" does not mean anything special.

I attach three different build logs, but you can find more failed
build logs here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-fsnotify.html

Once you make this to build reliably again, please consider uploading
the package in source-only form, so that we get pretty official build
logs here:

https://buildd.debian.org/status/package.php?p=golang-fsnotify

Thanks.

Attachment: golang-fsnotify_1.3.0-3_amd64-20160810T2339Z.gz
Description: application/gzip

Attachment: golang-fsnotify_1.3.0-3_amd64-20160818T193101Z.gz
Description: application/gzip

Attachment: golang-fsnotify_1.3.0-3_amd64-20160819T104418Z.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: golang-fsnotify
Source-Version: 1.3.0-4

We believe that the bug you reported is fixed in the latest version of
golang-fsnotify, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martín Ferrari <tin...@debian.org> (supplier of updated golang-fsnotify package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 23 Aug 2016 20:05:07 +0000
Source: golang-fsnotify
Binary: golang-github-fsnotify-fsnotify-dev golang-fsnotify-dev 
golang-github-go-fsnotify-fsnotify-dev
Architecture: source
Version: 1.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-fsnotify-dev - Transitional package for 
golang-github-fsnotify-fsnotify-dev
 golang-github-fsnotify-fsnotify-dev - File system notifications for Go
 golang-github-go-fsnotify-fsnotify-dev - Transitional package for 
golang-github-fsnotify-fsnotify-dev
Closes: 835057
Changes:
 golang-fsnotify (1.3.0-4) unstable; urgency=medium
 .
   * Disable flaky test. Closes: 835057.
Checksums-Sha1:
 f0b0e44b23bae113f6549155ce2f6929c1268f75 2371 golang-fsnotify_1.3.0-4.dsc
 660f8fe93af84e48c1a9e2f736a961efdc7d6f76 3608 
golang-fsnotify_1.3.0-4.debian.tar.xz
Checksums-Sha256:
 ddc8c30598d97ce0d660fe165cf29cecbe25944fa498785edacaa5a11fd5b1b5 2371 
golang-fsnotify_1.3.0-4.dsc
 042818dc236036819e8f0c20edd4d624284e89af07e52e003063cb4bc1b34423 3608 
golang-fsnotify_1.3.0-4.debian.tar.xz
Files:
 ffbc7cca5a72596af0bdbcb929795c12 2371 devel extra golang-fsnotify_1.3.0-4.dsc
 8c3e799299dfd2b5095984ca1d4f09d8 3608 devel extra 
golang-fsnotify_1.3.0-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXvK06AAoJEF3Y4L+Ro9PacAsQAMnZLJt2fO0H90YLcRVS3OVk
SQD2iSAubcO1TKpQMOYI0+6lYMwOghhTyWW83ayvhHrV0fxFpNQMZminMGzm3jHj
baOv2GZtu0wrdYsG4kCeAHYLsalvQ2JqP18flg/MPyB98WeBpPwdM2134T2IRWj6
3VuKZUBS0988D9k6vnmNBhpRjqh9XDozwIjwasmTCfYG3oxdWxuI3TD6Vqvd5vPX
RvHMJi0tZ3pjM2tTB8OM6gS3eiaaIE3MOp+KgeAYGXlT+vQXEktU3ivyw3023hp2
+OGQ96pn3P1qXxR4wIkiuBmjbzyfKtNxHjYAQUcZKyPQoSiFlucuvnCWXsqPLMNm
y/qBNjPRYgF+MnYtMNrLIzQqyIXsYTquFSG6hoDfDGHCLhr/pMGs2v2LiXH8bed8
by0MbHGXwmFbS6CXroDEza6DcuwoZfVdXhRVjT9vJvxo/gfRUFNU7iUr/y4dS2y9
ciDv+/IyW5dxxL3diBp+keV5q+iDNnMBIytCWQtG3iX0tFBMez9PIXzSLOgIdVkK
gOb6tQ2jI8jBA4SiHtcHewjQMbu5ilk2iUk7nRuubjviQp/9jWMHogkj/GG8LWr5
gPtv4URyNvReA1YVXewu41/brfDmvaMMCdMHyaRwdfTvivHUgjcGYfX3AT7lqy7y
oGvf/DkDYXfPTB74oOeO
=5djf
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to