Bug 720000 – dev-python/pyserial fails tests

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Agostino Sarubbo 2020-04-29 09:23:44 UTC]

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.

[Comment 1 Agostino Sarubbo 2020-04-29 09:23:53 UTC]

Created attachment 635152 [details]
build.log

build log and emerge --info

[Comment 2 Michał Górny 2020-04-29 10:46:50 UTC]

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

[Comment 3 Agostino Sarubbo 2020-04-29 11:04:14 UTC]

/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...

[Comment 4 Michał Górny 2020-04-29 11:14:49 UTC]

That mode= looks wrong.

$ mount | grep pts
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)

[Comment 5 Agostino Sarubbo 2020-04-29 11:27:02 UTC]

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

[Comment 6 Michał Górny 2020-05-01 14:53:50 UTC]

Could you try in console?

$ python -c 'import pty; print(pty.openpty())'

possibly for all Python versions.

[Comment 7 Agostino Sarubbo 2020-05-01 17:04:55 UTC]

(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)

[Comment 8 Michał Górny 2020-05-01 17:47:00 UTC]

Now, could you try that inside an ebuild?  Either create one or shove it on top of something existing.

[Comment 9 Agostino Sarubbo 2020-05-10 08:04:51 UTC]

It was an hw issue. It works for me now.