Your message dated Tue, 15 Dec 2020 22:09:34 -0500 with message-id <CAJ0cceax=KFKNVMAq-n=BxqDa34OE=tjj1b5eglguw_chwn...@mail.gmail.com> and subject line Re: snapd: FTBFS: FAIL: squashfs_test.go:130: SquashfsTestSuite.TestInstallSimpleNoCp has caused the Debian Bug report #964870, regarding snapd: FTBFS: FAIL: squashfs_test.go:130: SquashfsTestSuite.TestInstallSimpleNoCp 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.) -- 964870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: snapd Version: 2.44.1-2 Severity: serious While trying to rebuild the package, I noticed that one of the tests in the testsuite fails: === RUN Test ---------------------------------------------------------------------- FAIL: squashfs_test.go:130: SquashfsTestSuite.TestInstallSimpleNoCp squashfs_test.go:151: c.Check(linked, Equals, 1) ... obtained int = 0 ... expected int = 1 squashfs_test.go:152: c.Check(cmd.Calls(), HasLen, 0) ... obtained [][]string = [][]string{[]string{"cp", "-av", "/tmp/check-8449157405891831569/79/foo.snap", "/tmp/check-8449157405891831569/83/target.snap"}} ... n int = 0 OOPS: 36 passed, 1 FAILED --- FAIL: Test (0.38s) FAIL FAIL github.com/snapcore/snapd/snap/squashfs 0.391s -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages snapd depends on: ii adduser 3.118 ii apparmor 2.13.4-2 ii ca-certificates 20200601 ii gnupg 2.2.20-1 ii libapparmor1 2.13.4-2 ii libc6 2.30-8 ii libcap2 1:2.34-2 ii libseccomp2 2.4.3-1+b1 ii libudev1 245.6-1 ii openssh-client 1:8.3p1-1 ii squashfs-tools 1:4.4-2 ii systemd 245.6-1 ii udev 245.6-1 Versions of packages snapd recommends: ii gnupg 2.2.20-1 Versions of packages snapd suggests: ii zenity 3.32.0-5 -- Configuration Files: /etc/sudoers.d/99-snapd.conf [Errno 13] Permission denied: '/etc/sudoers.d/99-snapd.conf' -- no debconf information
--- End Message ---
--- Begin Message ---Hi Paul, that was quite a while ago, my test setup is an intel laptop running sbuilds via schroot sessions on directory chroots, nothing fancy. I can no longer reproduce this issue so I'm closing it. Thanks for following up! best, -rt On Tue, Dec 15, 2020 at 3:54 PM Paul Gevers <elb...@debian.org> wrote: > Hi Reinnard, > > [Release Team member here, reviewing RC bugs for bullseye.] > > On Sat, 11 Jul 2020 11:02:53 -0400 Reinhard Tartler > <siret...@tauware.de> wrote: > > While trying to rebuild the package, I noticed that one of the tests in > > the testsuite fails: > > Is/was this reproducible, or is this failure intermittent? We have had a > successful upload since, so not sure what to make of this bug. > > I checked reproducible-builds and it seems that this package FTBFS on > most architectures there, so maybe this is environment related. Can you > elaborate on your setup? > > Paul > > -- regards, Reinhard
--- End Message ---
