New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootstrap test suite stalls when run through Kyua with non-bash shells #24
Comments
From jmmv@google.com on August 16, 2011 13:13:20 This issue was updated by revision r200 . This is just a workaround for the problem described in this issue and we |
From jmmv@google.com on August 23, 2011 07:17:45 No reply from the GNU Autoconf guys. There is not much we can do, so postponing this ticket as 0.2 has to be released! Status: Blocked |
From julio@meroh.net on November 26, 2013 09:37:54 This issue was updated by revision 05583ef . This improvement may workaround the problem we experience when trying |
From julio@meroh.net on November 26, 2013 14:01:12 Status: Started |
From julio@meroh.net on November 26, 2013 14:33:35 This issue was updated by revision 2549ead . Bootstrap tests have been reenabled and this issue should now be fixed. |
From julio@meroh.net on November 26, 2013 14:36:07 I think this is now fixed, so closing. But I won't be surprised if we hit the problems again. Status: Fixed |
From jmmv@google.com on August 16, 2011 12:43:13
r186 added the bootstrap testsuite to the default Kyuafile suite. This is all fine when running the bootstrap testsuite with bash, but fails when using other shells. So far, I've reproduced the problem with Debian's dash (the default /bin/sh) and NetBSD's sh and ksh. Things work fine in OS X.
The problem is that the testsuite stalls because Kyua runs the testsuite in a different process group, and that process group is not a session leader. The testsuite issues a 'set -m' at some point unconditionally, and that blocks because the shell is not a session leader.
Clarification: http://mail-index.netbsd.org/netbsd-users/2011/08/15/msg008807.html Bug report: https://lists.gnu.org/archive/html/bug-autoconf/2011-08/msg00009.html I don't think we can do anything here regarding the testsuite other than waiting for Autotest to be "fixed" to not always run "set -m" (if they acknowledge this as a real issue).
For now, we probably ought to disable the reexecution of the bootstrap testsuite as part of the Kyua test suite.
Original issue: http://code.google.com/p/kyua/issues/detail?id=24
The text was updated successfully, but these errors were encountered: