Weird problem building zsh in local mock but not in koji

[Jason L Tibbitts III]

>>>>> "RM" == Roland McGrath <roland at redhat.com> writes:

RM> That is job control weirdness.  Something about the state of tty
RM> magic is different in the two different contexts where you run the
RM> test.

Unfortunately that level of magic is mostly beyond me.

RM> The things to look at are whether the tests are using a
RM> temporary pty

I do not really know how to determine that.  However, it simplifies
things to know that if there's any difference it's not in the spec but
in the environment in which mock is called.

RM> and what 'ps j' says about all the processes involved
RM> in the build/test (including mock and its layers of whatever before
RM> the rpmbuild).

Here's the forest from px axjf (sorry for long lines):

23843 10479 10479 10479 ?           -1 SNs      0   0:00  \_ sshd: tibbs [priv]
10479 10486 10479 10479 ?           -1 SN    7225   0:00  |   \_ sshd: tibbs at pts/3
10486 10487 10487 10487 pts/3    10527 SNs   7225   0:00  |       \_ -zsh
10487 10527 10527 10487 pts/3    10527 SN+   7225   0:00  |           \_ /bin/bash /home/tibbs/bin/dobuild /home/tibbs/work/extras-cvs/zsh/devel/zsh-4.3.10-4.fc13.src.rpm
10527 10530 10527 10487 pts/3    10527 SN+   7225   0:02  |               \_ /usr/bin/python -tt /usr/sbin/mock -r fedora-rawhide-x86_64 -v --rebuild /home/tibbs/work/extras-cvs/zsh/devel/zsh-4.3.10-4.fc13.src.rpm
10530 13230 13230 10487 pts/3    10527 TN    7225   0:00  |               |   \_ rpmbuild -bb --target x86_64 --nodeps builddir/build/SPECS/zsh.spec
13230 28410 13230 10487 pts/3    10527 TN    7225   0:00  |               |       \_ /bin/sh -e /var/tmp/rpm-tmp.5VZZeU
28410 28414 13230 10487 pts/3    10527 TN    7225   0:00  |               |           \_ make test
28414 28415 13230 10487 pts/3    10527 TN    7225   0:00  |               |               \_ /bin/sh -c cd Test ; make check
28415 28416 13230 10487 pts/3    10527 TN    7225   0:00  |               |                   \_ make check
28416 28505 13230 10487 pts/3    10527 TN    7225   0:00  |               |                       \_ /bin/sh -c if ZTST_testlist="`for f in ./*.ztst; \?           do echo $f; done`" \? ZTST_srcdir="." \? ZTST_exe=../Src/zsh \? ../Src/zsh +Z -f ./runtests.zsh; then \? sta
28505 28507 13230 10487 pts/3    10527 TN    7225   0:00  |               |                           \_ ../Src/zsh +Z -f ./runtests.zsh
28507 29888 13230 10487 pts/3    10527 TN    7225   0:00  |               |                               \_ ../Src/zsh +Z -f ./ztst.zsh ./B04read.ztst

Is any of that remotely helpful?  On the buildsys, a mock build (not for
zsh, but they should all start the same) looks sort of like this:

    1  3056  3055  3055 ?           -1 S        0 391:44 /usr/bin/python /usr/sbin/kojid --force-lock --verbose
 3056 17091 17091  3055 ?           -1 S        0   0:07  \_ /usr/bin/python /usr/sbin/kojid --force-lock --verbose
17091 17272 17091  3055 ?           -1 S      101   0:01      \_ /usr/bin/python -tt /usr/sbin/mock -r koji/dist-f13-build-653289-93821 --no-clean --target x86_64 --rebuild /mnt/koji/work/tasks/8377/1828377/kvirc-4.0.0-0.19.rc1.fc13.src.rpm
17272 25386 25386  3055 ?           -1 S      101   0:00          \_ rpmbuild -bb --target x86_64 --nodeps builddir/build/SPECS/kvirc.spec
25386 25413 25386  3055 ?           -1 S      101   0:00              \_ /bin/sh -e /var/tmp/rpm-tmp.vzHree
25413 25917 25386  3055 ?           -1 S      101   0:00                  \_ make -j4

and so on.  There are some obvious differences.

 - J<