This is an auto-filled bug because dev-python/pyserial fails tests. The issue was originally discovered on arm64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info.
Created attachment 635152 [details] build.log build log and emerge --info
This is another test failing with /dev/pts problems. It seems that your setup is broken. Could you try: https://stackoverflow.com/questions/43812333/oserror-out-of-pty-devices-with-python-sh#44370123
/dev/pts is mounted via: mount -o bind /dev/pts "${CHROOT_DIR}"/dev/pts and the rresult via mount is: none on /home/ago/arm64-unstable/dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000) so I have /dev/pts in the chroot...
That mode= looks wrong. $ mount | grep pts devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
I did unmount and mount and now looks ok: arm64 unstable (CHROOT) ~ $ mount | grep pts devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) I testes pyserial and fails in the same way
Could you try in console? $ python -c 'import pty; print(pty.openpty())' possibly for all Python versions.
(In reply to Michał Górny from comment #6) > Could you try in console? > > $ python -c 'import pty; print(pty.openpty())' > > possibly for all Python versions. Here i have 2.7, 3.6 and 3.8. For all versions I get: (3, 4)
Now, could you try that inside an ebuild? Either create one or shove it on top of something existing.
It was an hw issue. It works for me now.
