Changeset 39613

Timestamp:
Sep 29, 2007, 9:47:24 PM (15 years ago)
Author:
Noel Belcourt
Message:

Renamed variables used in timeout code so I don't make
silly mistakes like using a negative time for the select
timeout.

Also added the setrlimit call back in since the
named_condition_test occassionally consumes multiple cpus
worth of time. That is, when I ran this test -j4, I found
the named_condition test consuming 4 cpus worth of time so
after 300 seconds of elapsed time when the test timed out,
it had consumed almost 1200 seconds worth of cpu. While the
test is killed after the elapsed time expired, setting a hard
cpu limit ensures it's killed after consuming either -lx seconds
worth of cpu or -lx seconds of elapsed time.

(No files)

Note: See TracChangeset for help on using the changeset viewer.