From: Efraim Flashner <efraim@flashner.co.il>
To: Amin Bandali <bandali@gnu.org>
Cc: 34048@debbugs.gnu.org
Subject: [bug#34048] [PATCH] gnu: z3: Update to 4.8.4.
Date: Sun, 13 Jan 2019 09:52:25 +0200 [thread overview]
Message-ID: <20190113075225.GC2050@macbook41> (raw)
In-Reply-To: <87y37pqkfl.fsf@aminb.org>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Sat, Jan 12, 2019 at 10:57:02PM -0500, Amin Bandali wrote:
> Hi Leo,
>
> Thanks for the reply.
>
> [...]
>
> >
> > I tested this patch and found that arachne-pnr fails its test suite
> > after upgrading z3.
> >
> > Can you take a look?
> >
>
> Do you have test suite logs from before and after applying the patch?
> Running ‘guix build arachne-pnr’ seems to fail for me on both ‘master’
> and on my local ‘z3-4.8.4’ branch with my patch applied, so I’m not sure
> if it’s my patch that’s broken its test suite.
>
> Also, I’m a bit of Guix newbie, and I’m curious about if, and how, you
> test all the packages, only those that depend on Z3, or if you happened
> to stumble upon arachne-pnr’s failure.
>
'guix refresh -l z3' shows:
Building the following 2 packages would ensure 3 dependent packages are rebuilt: arachne-pnr@0.0-1-52e69ed20 cubicle@1.1.2
so in theory it's inexpensive to test the packages. Based on
arachne-pnr's version number, I'd check if there's a later commit that
doesn't fail the test suite.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-13 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 23:13 [bug#34048] [PATCH] gnu: z3: Update to 4.8.4 Amin Bandali
2019-01-12 23:30 ` Leo Famulari
2019-01-13 3:57 ` Amin Bandali
2019-01-13 7:52 ` Efraim Flashner [this message]
2019-01-13 15:16 ` Amin Bandali
2019-01-15 15:48 ` Danny Milosavljevic
2019-01-18 4:27 ` Amin Bandali
2019-01-18 16:14 ` bug#34048: " Leo Famulari
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190113075225.GC2050@macbook41 \
--to=efraim@flashner.co.il \
--cc=34048@debbugs.gnu.org \
--cc=bandali@gnu.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://git.savannah.gnu.org/cgit/guix.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).