all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Amin Bandali <bandali@gnu.org>
Cc: 34048-done@debbugs.gnu.org
Subject: bug#34048: [PATCH] gnu: z3: Update to 4.8.4.
Date: Fri, 18 Jan 2019 11:14:52 -0500	[thread overview]
Message-ID: <20190118161452.GA14834@jasmine.lan> (raw)
In-Reply-To: <87va2m7fpf.fsf@aminb.org>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

On Thu, Jan 17, 2019 at 11:27:40PM -0500, Amin Bandali wrote:
> With Danny’s changes the build phase for arachne-pnr passes but the
> check phase fails on one of the test cases, with or without my z3 4.8.4
> update patch.  I’ve attached the corresponding logs:
> 
> - gwa4kkg00rzp96jkqv52fzz4g197q4-arachne-pnr-0.0-2-840bdfdeb.drv.bz2:
>   with z3 4.8.3 (without my patch)
> - s1lqkz49nlp147m96bnn0d0yl21dgi-arachne-pnr-0.0-2-840bdfdeb.drv.bz2:
>   with z3 4.8.4 (with my patch)
> 
> A quick glance at the ediff of the two files, I didn’t see anything
> suggesting that the failure may be due to updating z3 from 4.8.3 to
> 4.8.4.  It might be a good idea to apply the z3 update patch and try
> resolving arachne-pnr’s test suite failure in a separate issue.

Thanks for investigating. I've pushed the z3 update as
6654f8c1447d80c4899c4234306801407315b31f

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-01-18 16:16 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
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             ` Leo Famulari [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190118161452.GA14834@jasmine.lan \
    --to=leo@famulari.name \
    --cc=34048-done@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.