From: "Dan Čermák" <dan.cermak@posteo.net>
To: Michael J Gruber <git@grubix.eu>, David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Date: Thu, 20 May 2021 15:05:46 +0000 [thread overview]
Message-ID: <87h7ixigxh.fsf@cgc-instruments.com> (raw)
In-Reply-To: <162152200602.42387.4634492844044681200.git@grubix.eu>
[-- Attachment #1.1: Type: text/plain, Size: 1734 bytes --]
Michael J Gruber <git@grubix.eu> writes:
> Dan Čermák venit, vidit, dixit 2021-05-20 16:30:40:
>> Michael J Gruber <git@grubix.eu> 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
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-05-20 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 8:16 Test failures with notmuch 0.32 and 0.32.1 on openSUSE Dan Čermák
2021-05-19 9:05 ` Michael J Gruber
2021-05-19 11:00 ` David Bremner
2021-05-20 6:10 ` Dan Čermák
2021-05-20 9:59 ` David Bremner
2021-05-20 14:16 ` Michael J Gruber
2021-05-20 14:30 ` Dan Čermák
2021-05-20 14:46 ` Michael J Gruber
2021-05-20 15:05 ` Dan Čermák [this message]
2021-05-20 19:54 ` Tomi Ollila
2021-05-20 14:28 ` Dan Čermák
2021-06-05 13:50 ` David Bremner
2021-06-08 8:24 ` Dan Čermák
2021-06-08 13:14 ` David Bremner
2021-06-08 14:13 ` Dan Čermák
2021-06-08 14:51 ` David Bremner
2021-08-28 15:20 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7ixigxh.fsf@cgc-instruments.com \
--to=dan.cermak@posteo.net \
--cc=david@tethera.net \
--cc=git@grubix.eu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).