Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_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!
https://wiki.archlinux.org/title/Bug_reporting_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!
FS#59065 - [mksh] check() fails
Attached to Project:
Community Packages
Opened by Erich Eckner (deepthought) - Tuesday, 19 June 2018, 13:04 GMT
Last edited by freswa (frederik) - Saturday, 17 October 2020, 23:17 GMT
Opened by Erich Eckner (deepthought) - Tuesday, 19 June 2018, 13:04 GMT
Last edited by freswa (frederik) - Saturday, 17 October 2020, 23:17 GMT
|
DetailsDescription:
FAIL ./check.t:utf8opt-3b Description: Ensure ±U on the command line is honoured, interactive shells unexpected stderr - got too much output wanted nothing got: /build/mksh/src/mksh/mksh: can't find: tty fd No such device or address /build/mksh/src/mksh/mksh: warning: won't have full job control /build/mksh/src/mksh/mksh: can't find: tty fd No such device or address /build/mksh/src/mksh/mksh: warning: won't have full job control Additional info: * package version(s) mksh-56.c-4 (git revision b4e37f1718f036a9ee2dd78d0c7648fbc97797f9) * config and/or log files etc. full log is attached Steps to reproduce: > git checkout b4e37f1718f036a9ee2dd78d0c7648fbc97797f9 > cd mksh/repos/community-x86_64 > extra-x86_64-build |
This task depends upon
Closed by freswa (frederik)
Saturday, 17 October 2020, 23:17 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce this while using devtools.
Saturday, 17 October 2020, 23:17 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce this while using devtools.
log
{
git -C ~/archlinux32/builder/work/repos/community/ archive b4e37f1718f036a9ee2dd78d0c7648fbc97797f9 -- mksh/repos/community-x86_64 | tar -x --strip-components=3
echo 'env:'
env
echo
extra-x86_64-build 2>&1
} | tee log
the second time (for which I opened that bug) it failed on this box here, without ssh/systemd interference, possibly inside a screen session,
the third time was on another box via ssh, because mine was busy,
I just tried here directly w/o screen/systemd/ssh/cron/... same failure, log is attached.
Maybe some env gets through, but shouldn't?