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