Hi! On 12/1/19 1:07 AM, Bob Tracy wrote: > All that being said, I'd *definitely* think twice about blindly changing > the sleep values. Again, you'll never see this issue on the "buildd" > systems. If I were the package maintainer, I'd reject this patch :-). > > (file is in "guile-2.2-2.2.6+1/test-suite/standalone" after extracting > the source package) > > --- test-guild-compile.orig 2019-11-30 17:56:39.276270948 -0600 > +++ test-guild-compile 2019-11-30 17:57:18.874959718 -0600 > @@ -23,10 +23,10 @@ > pid="$!" > > # Send SIGINT. > -sleep 2 && kill -INT "$pid" > +sleep 5 && kill -INT "$pid" > > # Wait for 'guild compile' to terminate. > -sleep 2 > +sleep 15 > > # Check whether there are any leftovers. > for file in "$target"*
I don't think there is anything wrong per se with increasing the test timeouts, it won't hurt on any architecture and build machine. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913