#1010964 yosys: autopkgtest regression

Package:
src:yosys
Source:
yosys
Submitter:
Adrian Bunk
Date:
2022-07-03 10:21:03 UTC
Severity:
serious
#1010964#5
Date:
2022-05-14 07:46:09 UTC
From:
To:
https://ci.debian.net/packages/y/yosys/unstable/amd64/

...
2.49. Executing BLIF backend.
ERROR: Found unmapped processes in module design_ice: unmapped processes are not supported in BLIF backend!
autopkgtest [12:35:12]: test ice: -----------------------]
autopkgtest [12:35:12]: test ice:  - - - - - - - - - - results - - - - - - - - - -
ice                  FAIL non-zero exit status 1
autopkgtest [12:35:12]: test ice:  - - - - - - - - - - stderr - - - - - - - - - -
ERROR: Found unmapped processes in module design_ice: unmapped processes are not supported in BLIF backend!
autopkgtest [12:35:12]: test smtbc: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 27049 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [12:35:15]: test smtbc: [-----------------------
autopkgtest [12:35:15]: test smtbc: -----------------------]
autopkgtest [12:35:15]: test smtbc:  - - - - - - - - - - results - - - - - - - - - -
smtbc                PASS
autopkgtest [12:35:15]: @@@@@@@@@@@@@@@@@@@@ summary
ice                  FAIL non-zero exit status 1
smtbc                PASS



In a short test with 0.17, this appear to fix it.
#1010964#12
Date:
2022-06-17 05:22:17 UTC
From:
To:
[Adrian Bunk]

If the RC fix is to upgrade, I hope it will happen soon to get the FPGA
programming tool chain back into testing.

CC to the uploaders, in case they are not following the Debian Science
mailing list closely.
#1010964#17
Date:
2022-06-17 11:48:24 UTC
From:
To:
[Daniel Gröber]

Why do you believe so?  That is not what I read from
<URL: https://tracker.debian.org/pkg/yosys >.  It claim #1010964 is the
reason yosys is thrown out of testing.

Is upgrading to 0.18 out of the question?
#1010964#22
Date:
2022-06-17 11:55:07 UTC
From:
To:
Hi Petter,

I think #1008718 is why it was removed and #1010964 is why it can't be
re-introduced (yet). Even if I upload 0.17 or just the autopkgtest fix
it'll still likely fail on mips64el again so it whouldn't go through anyway
until that is fixed/worked-around.

No, not at all. Just depends on how annoying rebasing the patches ends up
being.
#1010964#27
Date:
2022-06-17 11:40:49 UTC
From:
To:
Hi Petter,

FYI the removal from testing was due to #1008718 (build failure on
mips64el). I never had enough time to debug what's going on there and the
porter boxes for that arch being slow as hell doesn't help.

I think I'll just exclude the mips64el arch in the yosys package and be
done with it. Right after I figure out how to do that :)
#1010964#32
Date:
2022-07-03 06:49:38 UTC
From:
To:
[Daniel Gröber]

I notice the new upload of 0.18 already happened, which is very nice to
see.  But this bug was not closed in debian/changelog.  Does this mean
bug #1010964 is not solved?

Also, remember to ask ftpmasters to remove any mips64el binaries from
unstable when excluding it for the package, if you have not done so
already.

<URL: https://tracker.debian.org/pkg/yosys > show a few obstacles for
entering testing.
#1010964#43
Date:
2022-07-03 10:17:21 UTC
From:
To:
Thanks for the reminder. The mips64el RM request is Bug#1014274 and seeing
that autopkgtest seems to succeed now I'm closing this bug.