On 03/22/2017 03:19 PM, Quanah Gibson-Mount wrote:

Even better is to use the SLEEP variables instead of hard coded values. Then they can be overridden in the test environment if necessary for specific VMs.

At the moment we have:

quanah@ub16:~/git/openldap/openldap-head/tests/scripts$ grep SLEEP defines.sh SLEEP0=${SLEEP0-1} SLEEP1=${SLEEP1-7} SLEEP2=${SLEEP2-15}

It may be useful to add things like SLEEP10, SLEEP20, etc, and rebase tests off of that. 1/7/15 seem rather odd increments (no pun intended!).

This could well be a very good idea for broader reasons, but it probably would be less desirable as a sole solution for this particular situation, at least for my use case. In this case, I'm backporting 2.4.44 for zesty to 14.04 LTS. Ideally, I want this to be a clean rebuild, without any code changes. I'm especially reluctant to maintain a customized package for something that doesn't affect the behavior of the actual software. So having more variable(s) that need to be tuned, and thus changed from the vanilla Ubuntu package, isn't too appealing :-)

Hopefully there's an agreeable solution to this issue that will make it work for everyone out of the box. In any case, I appreciate your and Howard's responses to this!

Regards,

-Kartik