Follow-up Comment #5, bug #15719 (project make):
greg~
In my first mail to Paul, I also mentioned the Cygwin erratic failures in
features/parallelism. However, at that time I was using GNU make 3.80. With
GNU make 3.81beta4, it seems to me it's harder to reproduce the random
failures since verstion 3.81beta4 runs a bit faster. :=)
> It is only TEST #5 which fails, but with somewhat different
> output; my guess is that creating load conditions, running
> other applications like video, while the test is running,
> helps reproduce the failure.
In fact, the tests in features/parallelism is somewhat fragile especially for
very slow machine (or fast machine but with heavy load). They make extensive
use of "sleep 1", "sleep 2", and etc., to do synchronization and assume that
the user's machine runs fast enough. For this reason, it's not a
Cygwin-specific problem IMHO.
> It does NOT work reliably under Cygwin, in my experience.
I'm guessing it's probably not a bug in GNU make, but a "bug" in the test
suit itself. AFAIK, there's no easy way to overcome this problem, hence it's
mostly the user's responsibility not to run the test suit either on very slow
machines or when the system load is pretty high. Yes, it's not an ultimate
solution. :/
Regards,
Agent
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=15719>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
