Reduce the stress level of the MAILBOX tests by a factor of 10.
Reasons:
a) As contrib tests are run as part of a normal SBCL build, the
mailbox tests are executed each time SBCL is built. And they
really result in a few minutes of 100% cpu usage and high load
averages because of many simultaneously running threads.
b) On BSD platforms, the tests were reported several times in past
to fail. From what I'm told (and if I remember correctly), the
issue is, however, not necessarily concurrency bugs, but a
coarser SLEEP granularity than on Linux platform.
(deftest mailbox.single-producer-single-consumer
(test-mailbox-producers-consumers :n-senders 1
:n-receivers 1
- :n-messages 10000)
- (:received . 10000)
+ :n-messages 1000)
+ (:received . 1000)
(:garbage . 0)
(:errors . 0)
(:timeouts . 0))
(deftest mailbox.single-producer-multiple-consumers
(test-mailbox-producers-consumers :n-senders 1
:n-receivers 100
- :n-messages 10000)
- (:received . 10000)
+ :n-messages 1000)
+ (:received . 1000)
(:garbage . 0)
(:errors . 0)
(:timeouts . 0))
(deftest mailbox.multiple-producers-single-consumer
- (test-mailbox-producers-consumers :n-senders 100
+ (test-mailbox-producers-consumers :n-senders 10
:n-receivers 1
:n-messages 100)
- (:received . 10000)
+ (:received . 1000)
(:garbage . 0)
(:errors . 0)
(:timeouts . 0))
(deftest mailbox.multiple-producers-multiple-consumers
(test-mailbox-producers-consumers :n-senders 100
:n-receivers 100
- :n-messages 10000)
- (:received . 1000000)
+ :n-messages 1000)
+ (:received . 100000)
(:garbage . 0)
(:errors . 0)
(:timeouts . 0))
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.39.16"
+"1.0.39.17"