Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55078 - [python-libnacl] check() fails

Attached to Project: Community Packages
Opened by Erich Eckner (deepthought) - Wednesday, 09 August 2017, 08:55 GMT
Last edited by Ivy Foster (escondida) - Friday, 11 October 2019, 19:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

If trying to build the package in a clean chroot, check() fails with:
==> Starting check()...
test_gcm_aead (unit.test_aead.TestAEAD) ... /startdir/PKGBUILD: line 30: 420 Illegal instruction (core dumped) python -m unittest discover --start-directory tests -v
==> ERROR: A failure occurred in check().
Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/staging-x86_64/erich/build

Additional info:
* package version(s)
python-libnacl-1.5.2-1
git revision ec650e449fa9d46972765f47490fef52d14aa320
* config and/or log files etc.
full log is attached

Steps to reproduce:
> git clone https://git.archlinux.org/svntogit/community.git/
> cd community
> git checkout ec650e449fa9d46972765f47490fef52d14aa320
> cd python-libnacl/repos/community-any
> staging-x86-build
   log (4.4 KiB)
This task depends upon

Closed by  Ivy Foster (escondida)
Friday, 11 October 2019, 19:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  Time heals all wounds.
Comment by Doug Newgard (Scimmia) - Thursday, 10 August 2017, 03:13 GMT
No problem here. What processor?
Comment by Erich Eckner (deepthought) - Thursday, 10 August 2017, 04:41 GMT
This was on a:
Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz

/proc/cpuinfo is attached

Do you need any other infos?
   cpu (3.6 KiB)
Comment by Doug Newgard (Scimmia) - Thursday, 10 August 2017, 15:14 GMT
That excludes any of the obvious answers, then.
Comment by Andreas Baumann (andreas_baumann) - Thursday, 14 September 2017, 19:28 GMT
See https://bbs.archlinux32.org/viewtopic.php?pid=219#p219, I think, I found it (at least the test works).
I'll report upstreams..
Comment by Andreas Baumann (andreas_baumann) - Thursday, 14 September 2017, 19:29 GMT
Actually, mine is a "Python ctypes parameter passing bug", not a "missing AES on CPU" bug. I should have opened a new bug, sorry..
Comment by Andreas Baumann (andreas_baumann) - Thursday, 14 September 2017, 19:33 GMT
The AES bug I don't completly understand: libsodium does a check for AES support in the compiler,
but I fear, they don't acually check the CPU capabilities..
Comment by Ivy Foster (escondida) - Thursday, 10 October 2019, 23:38 GMT
deepthought, do you still run into this issue?
Comment by Erich Eckner (deepthought) - Friday, 11 October 2019, 06:25 GMT
I just checked, and the error has vanished here, too.
This can be closed, thanks.
Comment by Ivy Foster (escondida) - Friday, 11 October 2019, 19:30 GMT
Thank you!

Loading...