Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > Hi David, > > David Bremner writes: > >> Dan Čermák writes: >> >>> >>> yes, in my "home project": >>> https://build.opensuse.org/package/live_build_log/home:dancermak:branches:devel:libraries:c_c++/notmuch/openSUSE_Factory/x86_64 >> >> Thanks, I took a second look at this, and the underlying issue is that >> the SMIME related tests depend on the openssl binary, which isn't >> available in your build environment. We can (for a future point release) >> try to make the test suite report this better and skip the tests, but >> for know I suggest either installing openssl or manually skipping the >> tests in question. The latter is doccumented in test/README > > Thanks a lot! > > I have added openssl into the buildroot and now the tests run > successfully on Tumbleweed, but not on Leap 15.2 and 15.3 where some > Emacs tests are failing now: I'm marking this fixed by dda50ede050caa8aef5dda68d41b30b6c213c67d which is in 0.32.2. d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > *ERROR*: Symbol’s function definition is void: seq-some > --8<---cut here---end--->8--- > > Both versions of Leap are running Emacs 25.3, so maybe that's the issue? > Likely so. The autoload for seq-some was (I think) added in emacs 27, but the function itself exists since 2015, so it should be fixable. ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Hi David, David Bremner writes: > Dan Čermák writes: > >> >> yes, in my "home project": >> https://build.opensuse.org/package/live_build_log/home:dancermak:branches:devel:libraries:c_c++/notmuch/openSUSE_Factory/x86_64 > > Thanks, I took a second look at this, and the underlying issue is that > the SMIME related tests depend on the openssl binary, which isn't > available in your build environment. We can (for a future point release) > try to make the test suite report this better and skip the tests, but > for know I suggest either installing openssl or manually skipping the > tests in question. The latter is doccumented in test/README Thanks a lot! I have added openssl into the buildroot and now the tests run successfully on Tumbleweed, but not on Leap 15.2 and 15.3 where some Emacs tests are failing now: --8<---cut here---start->8--- T310-emacs: Testing emacs interface FAIL notmuch-fcc-dirs set to a list (with match) --- T310-emacs.30.EXPECTED 2021-06-08 14:01:41.14400 + +++ T310-emacs.30.OUTPUT2021-06-08 14:01:41.14400 + @@ -1,5 +0,0 @@ -From: Notmuch Test Suite -To: -Subject: -Fcc: /home/abuild/rpmbuild/BUILD/notmuch-0.32.1/test/tmp.T310-emacs/mail/sent-list-match ---text follows this line-- *ERROR*: Symbol’s function definition is void: seq-some FAIL notmuch-fcc-dirs set to a list (catch-all) --- T310-emacs.31.EXPECTED 2021-06-08 14:01:41.17200 + +++ T310-emacs.31.OUTPUT2021-06-08 14:01:41.17200 + @@ -1,5 +0,0 @@ -From: Notmuch Test Suite -To: -Subject: -Fcc: /home/abuild/rpmbuild/BUILD/notmuch-0.32.1/test/tmp.T310-emacs/mail/sent-list-catch-all ---text follows this line-- *ERROR*: Symbol’s function definition is void: seq-some FAIL notmuch-fcc-dirs set to a list (no match) --- T310-emacs.32.EXPECTED 2021-06-08 14:01:41.2 + +++ T310-emacs.32.OUTPUT2021-06-08 14:01:41.2 + @@ -1,4 +0,0 @@ -From: Notmuch Test Suite -To: -Subject: ---text follows this line-- *ERROR*: Symbol’s function definition is void: seq-some --8<---cut here---end--->8--- Both versions of Leap are running Emacs 25.3, so maybe that's the issue? Cheers, Dan ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > > yes, in my "home project": > https://build.opensuse.org/package/live_build_log/home:dancermak:branches:devel:libraries:c_c++/notmuch/openSUSE_Factory/x86_64 Thanks, I took a second look at this, and the underlying issue is that the SMIME related tests depend on the openssl binary, which isn't available in your build environment. We can (for a future point release) try to make the test suite report this better and skip the tests, but for know I suggest either installing openssl or manually skipping the tests in question. The latter is doccumented in test/README d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Hi David, David Bremner writes: > Dan Čermák writes: > >> David Bremner writes: >> >> [snip...] >>> >>> Thanks. What about python and gnupg versions? >> >> That would be: >> Python 3.8.10 >> gpg (GnuPG) 2.2.27 > > I installed openSUSE tumbleweed (current as of June 3) in a KVM vm, and > the tests are passing. There are some recurring issues with parallel > tests in this vm (I think some timeouts with gdb), but with > NOTMUCH_TEST_SERIALIZE=t or with no parallel in the VM, everything > passes fine both on master and 0.32.1 (from git checkouts or tarball). > > The log I checked [1] _was_ running the tests in parallel. > > Can you point me to a full log from a failing non-parallel test run in > tumbleweed? yes, in my "home project": https://build.opensuse.org/package/live_build_log/home:dancermak:branches:devel:libraries:c_c++/notmuch/openSUSE_Factory/x86_64 Cheers, Dan ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > David Bremner writes: > > [snip...] >> >> Thanks. What about python and gnupg versions? > > That would be: > Python 3.8.10 > gpg (GnuPG) 2.2.27 I installed openSUSE tumbleweed (current as of June 3) in a KVM vm, and the tests are passing. There are some recurring issues with parallel tests in this vm (I think some timeouts with gdb), but with NOTMUCH_TEST_SERIALIZE=t or with no parallel in the VM, everything passes fine both on master and 0.32.1 (from git checkouts or tarball). The log I checked [1] _was_ running the tests in parallel. Can you point me to a full log from a failing non-parallel test run in tumbleweed? Of course ideally the parallel test suite would work too, but one step at a time. [1]: https://build.opensuse.org/package/live_build_log/openSUSE:Factory/notmuch/standard/x86_64 ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
On Thu, May 20 2021, Michael J. Gruber wrote: > David Bremner venit, vidit, dixit 2021-05-20 11:59:50: >> Dan Čermák writes: >> >> > >> > Right, I mistakenly thought this would grab the test database. Is that >> > one no longer necessary? >> > >> >> Ah, that's a different make target, which is indeed no longer necessary >> (we don't do the relevant tests any more). >> >> >> 1) can you duplicate the problem without running the tests in parallel? >> > >> > They don't run in parallel, as gnu parallel is not installed inside the >> > container. So: yes, I can. >> >> OK, it was a long shot, but gpgsm has some known issues with parallel tests. >> >> >> 2) What are the versions of the dependencies you are building with? >> > >> > emacs-el-27.2-1.2.noarch >> >> [snip...] >> >> Thanks. What about python and gnupg versions? >> > > So, I ran the container using buildah on Fedora 33 (without the make > corpus_download). Again, I'm not a container guy, so I don't know what > the influence of the host is. But: > > What ist the shell in that container? > > I don't see T356 failing, but: > > T050-new.36 (Xapian exception: read only files) can read all files, so > either chmod u-w fails or xapian can write the db anyway. The read-obly file failures happen due to running containers in "rootless" mode; even the files are chmod'd read-only the files can still be written there (IMO that is a bug in podman...) try: $ echo foo > bar $ chmod 400 bar $ cat bar foo $ echo foo >> bar zsh: permission denied: bar $ podman unshare # echo foo >> bar # cat bar foo foo # exit $ cat bar foo foo $ echo foo >> bar zsh: permission denied: bar I've been running some tests in various (podman) containers, and seen that -- cannot recall now If I've seen all the others below... Tomi > > T050-new.37 and the T060-count.14 are gdb related and too much for me to > wrap my head around :| > > T150 "Xapian exception: read only files" is again chmod u-w > > Do they fail to fail (fail to throw) because the tests run as root (or > wheel) inside the container? > > T380 clearly fails because the shell does not know arithmetic expansion. > > The rest passes as expected, except for ruby tests (skipped), known broken > tests and the two USERNAME@FQDN issues which were fixed recently. > > 1486/1497 tests passed. > 4 broken tests failed as expected. > 7 tests failed. > All tests in 2 files skipped. > > > Maybe someone switched their default shell ;) > > Michael > > P.S.: I assume this during build is buildah-related: > dbus-daemon[427]: [session uid=0 pid=427] > org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to > 65536: Operation not permitted ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Michael J Gruber writes: > Dan Čermák venit, vidit, dixit 2021-05-20 16:30:40: >> Michael J Gruber writes: >> >> > >> > So, I ran the container using buildah on Fedora 33 (without the make >> > corpus_download). Again, I'm not a container guy, so I don't know what >> > the influence of the host is. But: >> > >> > What ist the shell in that container? >> >> It should be bash in the final container, but it could be that buildah >> is not using bash to run the actual build. >> >> >> > I don't see T356 failing, but: >> >> I'll be dammed. That test was failing yesterday in the container build >> and today it is succeeding. >> >> Unfortunately, it is still failing in the Open Build Service :-( > > With each fresh look it's getting more mysterious ... In > > https://build.opensuse.org/public/build/home:dancermak:branches:devel:libraries:c_c++/openSUSE_Factory/x86_64/notmuch/_log > > I see that tests are run with gnu parallel and not sequentially. The only > FAILs are the sig_uid ones in T356. > > So, apparantly, the local buildah run does something different from OBS. Yes it does. But I have tried to run the build without gnu parallel in the buildroot and even then T356-protected-headers fail. Unfortunately there are some differences between running the build in the build service and with buildah. First, the packages that buildah uses are from the released Tumbleweed snapshot, those in the Build Service are the current development ones. And the build service builds everything in a isolated VM, while buildah is a container builder. It shouldn't make a difference, but often enough it results in subtle changes. Cheers, Dan signature.asc Description: PGP signature ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák venit, vidit, dixit 2021-05-20 16:30:40: > Michael J Gruber writes: > > > > > So, I ran the container using buildah on Fedora 33 (without the make > > corpus_download). Again, I'm not a container guy, so I don't know what > > the influence of the host is. But: > > > > What ist the shell in that container? > > It should be bash in the final container, but it could be that buildah > is not using bash to run the actual build. > > > > I don't see T356 failing, but: > > I'll be dammed. That test was failing yesterday in the container build > and today it is succeeding. > > Unfortunately, it is still failing in the Open Build Service :-( With each fresh look it's getting more mysterious ... In https://build.opensuse.org/public/build/home:dancermak:branches:devel:libraries:c_c++/openSUSE_Factory/x86_64/notmuch/_log I see that tests are run with gnu parallel and not sequentially. The only FAILs are the sig_uid ones in T356. So, apparantly, the local buildah run does something different from OBS. Michael ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Michael J Gruber writes: > > So, I ran the container using buildah on Fedora 33 (without the make > corpus_download). Again, I'm not a container guy, so I don't know what > the influence of the host is. But: > > What ist the shell in that container? It should be bash in the final container, but it could be that buildah is not using bash to run the actual build. > I don't see T356 failing, but: I'll be dammed. That test was failing yesterday in the container build and today it is succeeding. Unfortunately, it is still failing in the Open Build Service :-( Cheers, Dan signature.asc Description: PGP signature ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
David Bremner writes: [snip...] > > Thanks. What about python and gnupg versions? That would be: Python 3.8.10 gpg (GnuPG) 2.2.27 signature.asc Description: PGP signature ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
David Bremner venit, vidit, dixit 2021-05-20 11:59:50: > Dan Čermák writes: > > > > > Right, I mistakenly thought this would grab the test database. Is that > > one no longer necessary? > > > > Ah, that's a different make target, which is indeed no longer necessary > (we don't do the relevant tests any more). > > >> 1) can you duplicate the problem without running the tests in parallel? > > > > They don't run in parallel, as gnu parallel is not installed inside the > > container. So: yes, I can. > > OK, it was a long shot, but gpgsm has some known issues with parallel tests. > > >> 2) What are the versions of the dependencies you are building with? > > > > emacs-el-27.2-1.2.noarch > > [snip...] > > Thanks. What about python and gnupg versions? > So, I ran the container using buildah on Fedora 33 (without the make corpus_download). Again, I'm not a container guy, so I don't know what the influence of the host is. But: What ist the shell in that container? I don't see T356 failing, but: T050-new.36 (Xapian exception: read only files) can read all files, so either chmod u-w fails or xapian can write the db anyway. T050-new.37 and the T060-count.14 are gdb related and too much for me to wrap my head around :| T150 "Xapian exception: read only files" is again chmod u-w Do they fail to fail (fail to throw) because the tests run as root (or wheel) inside the container? T380 clearly fails because the shell does not know arithmetic expansion. The rest passes as expected, except for ruby tests (skipped), known broken tests and the two USERNAME@FQDN issues which were fixed recently. 1486/1497 tests passed. 4 broken tests failed as expected. 7 tests failed. All tests in 2 files skipped. Maybe someone switched their default shell ;) Michael P.S.: I assume this during build is buildah-related: dbus-daemon[427]: [session uid=0 pid=427] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > > Right, I mistakenly thought this would grab the test database. Is that > one no longer necessary? > Ah, that's a different make target, which is indeed no longer necessary (we don't do the relevant tests any more). >> 1) can you duplicate the problem without running the tests in parallel? > > They don't run in parallel, as gnu parallel is not installed inside the > container. So: yes, I can. OK, it was a long shot, but gpgsm has some known issues with parallel tests. >> 2) What are the versions of the dependencies you are building with? > > emacs-el-27.2-1.2.noarch [snip...] Thanks. What about python and gnupg versions? d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
David Bremner writes: > Dan Čermák writes: > >> RUN wget https://notmuchmail.org/releases/notmuch-${NOTMUCH_VERSION}.tar.xz >> && \ >> xz -dc notmuch-${NOTMUCH_VERSION}.tar.xz | tar -xof - && \ >> cd notmuch-${NOTMUCH_VERSION} && \ >> ./configure \ >> --prefix=/usr \ >> --sysconfdir=/etc \ >> --datadir=/usr/share \ >> --includedir=/usr/include \ >> --libdir=/usr/lib64 \ >> --libexecdir=/usr/libexec \ >> --localstatedir=/var \ >> --mandir=/usr/share/man \ >> --infodir=/usr/share/info \ >> --disable-dependency-tracking \ >>--without-zsh-completion && \ >> make download-corpus > > No idea (yet) about the real problem here, but note that you most likely don't > want to run "make download-corpus". That downloads the 400M performance > test corpus, which is only used by the performance tests. I'm guessing > your build does not run the performance tests. Right, I mistakenly thought this would grab the test database. Is that one no longer necessary? > > 1) can you duplicate the problem without running the tests in parallel? They don't run in parallel, as gnu parallel is not installed inside the container. So: yes, I can. > 2) What are the versions of the dependencies you are building with? emacs-el-27.2-1.2.noarch emacs-nox-27.2-1.2.x86_64 gdb-10.1-7.1.x86_64 info-6.7-2.5.x86_64 man-2.8.4-14.4.x86_64 pkgconf-pkg-config-1.7.3-3.1.x86_64 python38-Sphinx-3.5.4-1.1.noarch python38-base-3.8.10-1.2.x86_64 dtach-v0.9+2.748020b-2.1.x86_64 gmime-devel-3.2.7-1.7.x86_64 libgcrypt-cavs-1.9.3-1.1.x86_64 libtalloc-devel-2.3.2-1.1.x86_64 libxapian-devel-1.4.18-1.4.x86_64 makeinfo-6.7-2.5.x86_64 valgrind-devel-3.17.0-1.1.x86_64 gcc10-c++-10.3.0+git1587-1.2.x86_64 gcc-10-3.3.x86_64 gcc10-10.3.0+git1587-1.2.x86_64 gcc-c++-10-3.3.x86_64 make-4.3-2.22.x86_64 makeinfo-6.7-2.5.x86_64 wget-1.21.1-1.5.x86_64 xz-5.2.5-1.18.x86_64 tar-1.34-1.4.x86_64 bash-5.1.4-2.1.x86_64 xapian-core-1.4.18-1.4.x86_64 openssl-1_1-1.1.1k-2.1.x86_64 openssl-1.1.1k-1.1.noarch signature.asc Description: PGP signature ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák writes: > RUN wget https://notmuchmail.org/releases/notmuch-${NOTMUCH_VERSION}.tar.xz > && \ > xz -dc notmuch-${NOTMUCH_VERSION}.tar.xz | tar -xof - && \ > cd notmuch-${NOTMUCH_VERSION} && \ > ./configure \ > --prefix=/usr \ > --sysconfdir=/etc \ > --datadir=/usr/share \ > --includedir=/usr/include \ > --libdir=/usr/lib64 \ > --libexecdir=/usr/libexec \ > --localstatedir=/var \ > --mandir=/usr/share/man \ > --infodir=/usr/share/info \ > --disable-dependency-tracking \ >--without-zsh-completion && \ > make download-corpus No idea (yet) about the real problem here, but note that you most likely don't want to run "make download-corpus". That downloads the 400M performance test corpus, which is only used by the performance tests. I'm guessing your build does not run the performance tests. 1) can you duplicate the problem without running the tests in parallel? 2) What are the versions of the dependencies you are building with? d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Dan Čermák venit, vidit, dixit 2021-05-19 10:16:39: > Hi list, > > notmuch 0.32 recently stopped building on openSUSE Leap and Tumbleweed > due to failures in the test suite. It now consistently fails in > T356-protected-headers: > > FAIL verify signed PKCS#7 subject (multipart-signed) signer User ID > sig_uid: object not found: > data[0][0][0]["crypto"]["signed"]["status"][0]["userid"] > PASS verify signed PKCS#7 subject (onepart-signed) > FAIL verify signed PKCS#7 subject (onepart-signed) signer User ID > sig_uid: object not found: > data[0][0][0]["crypto"]["signed"]["status"][0]["userid"] > PASS confirm signed and encrypted PKCS#7 subject (sign+enc) > FAIL confirm signed and encrypted PKCS#7 subject (sign+enc) signer User ID > sig_uid: object not found: > data[0][0][0]["crypto"]["signed"]["status"][0]["userid"] > PASS confirm signed and encrypted PKCS#7 subject (sign+enc+legacy-disp) > FAIL confirm signed and encrypted PKCS#7 subject (sign+enc+legacy-disp) > signer User ID > sig_uid: object not found: > data[0][0][0]["crypto"]["signed"]["status"][0]["userid"] > > > Unfortunately, I don't really know what the issue at hand is and how to > debug it. If anyone could help me out here, I'd be very grateful. I have > attached a Dockerfile that you can use to reproduce this issue (simply > build it using your favorite container build tool, e.g. > `buildah bud --layers --build-arg NOTMUCH_VERSION=0.32`). Note that in > the container build additional tests fail in contrast to building the > rpm. I'm no docker guy, sorry. But the failures indicate that the output of signature verification changed (unless local variables stopped being local;) ). Can you check whether notmuch show --decrypt=true --format=json "id:smime-${variant}@protected-headers.example" for one of the variants (such as sign+enc) gives proper output but misses sig_uid? You would have to that with GNUPGHOME="${TEST_TMPDIR}/gnupg" etc. Maybe gpgsm's output changed? Michael ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org